# Sending Accounts

## Use case

Check your connected mailboxes before creating outreach emails or sequences.

## Endpoint

```http
GET https://api-public.clodo.ai/api/public/v1/email/accounts/
```

Send your API key in the `x-api-key` header. See [Authentication](https://docs.clodo.ai/api-reference/authentication).

## Pricing

See [Credits & Pricing](https://docs.clodo.ai/guides/credits-and-pricing) for credit costs and charging behavior.

## Errors

For error responses and retry guidance, see [Handling Errors](https://docs.clodo.ai/api-reference/errors).

`GET /api/public/v1/email/accounts/` — sync. Free.

Outreach emails send from **your own connected mailbox** (Google, Microsoft, or SMTP) — your address, your sending reputation. Accounts are connected and managed in the Clodo web app (Settings → Email Accounts); the API surface is read-only. Use this endpoint to check that a usable inbox exists before creating emails.

## Response

```json
{
  "accounts": [
    {
      "id": "ea_65006cf5b9b8c2af",
      "email": "you@yourcompany.com",
      "type": "google",
      "connected": true,
      "sending_enabled": true,
      "daily_limit": 35,
      "sent_today": 12,
      "health": "healthy"
    }
  ]
}
```

| Field | Notes |
|---|---|
| `id` | Stable `ea_...` handle. Pass as `from_account` when creating an email to pin the sender. |
| `type` | `google`, `microsoft`, or `smtp`. |
| `connected` | `false` means the account needs attention in the web app (e.g. re-auth). |
| `daily_limit` | Effective sends allowed today (accounts warm up gradually and throttle on poor engagement). |
| `health` | `healthy`, or a state describing what needs fixing (e.g. `reauth_required`). |

If the list is empty (or nothing is `connected` + `sending_enabled`), `POST /emails/` returns `409 conflict` — connect an inbox in the web app first.

## See also

- [Outreach Emails](https://docs.clodo.ai/api-reference/endpoint/outreach-emails)