# Connection status

> What each account status means and how to react to it.

Every account carries a `status`. Because outreach runs against a live platform, status can change on its own — build for it.

## Statuses

| Status | Meaning | What to do |
| --- | --- | --- |
| `connected` | The account is operational and ready for methods. | Nothing. |
| `connecting` | A hosted link was created but the user hasn't finished. | Wait, or resend the link. |
| `disconnected` | The session is no longer valid. | [Reconnect](/manage-accounts#reconnect-an-account) the account. |

## Checking status

Poll the account, or — better — subscribe to [webhooks](/webhooks) and react to `account.connected` and `account.disconnected` events.

```bash
curl https://api.correctinbox.com/v1/accounts/acc_8f21c0 \
  -H "X-API-KEY: $CORRECTINBOX_API_KEY"
```

```js
const acc = await (
  await fetch("https://api.correctinbox.com/v1/accounts/acc_8f21c0", {
    headers: { "X-API-KEY": process.env.CORRECTINBOX_API_KEY },
  })
).json();
if (acc.status === "disconnected") {
  // prompt the user to reconnect
}
```

```python
acc = requests.get(
    "https://api.correctinbox.com/v1/accounts/acc_8f21c0",
    headers={"X-API-KEY": os.environ["CORRECTINBOX_API_KEY"]},
).json()
```

## Limited access on new accounts

A `connected` account can still have **limited access** to some actions. New or low‑standing provider accounts are often restricted from people search and high‑volume actions until they are more established on the platform.

This shows up as **empty results** (for example, a search that returns nothing on a real keyword), not as an error. It is a property of that account on the provider, not a problem with your request or the API. To resolve it, let the account mature — complete its profile, make a few connections, use it normally — or run the action on a more established account.
