---
title: "Whether a LinkedIn sender is connected"
method: GET
path: "/api/v1/senders"
---

# Whether a LinkedIn sender is connected

`GET /api/v1/senders`

## Request

- Base URL: `https://www.easeclaw.com`
- URL: `https://www.easeclaw.com/api/v1/senders`
- Auth: HTTP bearer

Read-only status of the account's LinkedIn sender. Its state and when it last reported in. Campaigns can be built, filled and edited without one; approved outreach only leaves once the owner connects a sender in their dashboard. Connecting and disconnecting stay human: there is no endpoint here that does either. No plan floor. Requires an outreach-scope API key.

## Response `200`

The sender's status

- object
  - `sender` object
    - `status` 'not_connected' | 'connecting' | 'connected' | 'checkpoint' | 'disconnected'
    - `country` string, nullable
    - `connectedAt` string, date-time, nullable
    - `lastEventAt` string, date-time, nullable
    - `stale` boolean: True when a sign-in has sat in 'connecting' for 30+ minutes with nothing heard back: it is not going to land, start it again
  - `available` boolean: Whether the cloud sending path is configured at all

## Other responses

- `401`: Error
- `402`: Error
- `403`: The key is not outreach-scoped (code outreach_scope_required). Campaign paths need a key minted with the outreach scope at https://www.easeclaw.com/leads/api. The scope cannot be widened on an existing key.
- `500`: Error
- `503`: Error

---

[API](https://skmtc.dev/easeclaw/apis/easeclaw-api.md) · [All operations](https://skmtc.dev/easeclaw/apis/easeclaw-api/llms.txt) · [OpenAPI document](https://skmtc.dev/easeclaw/apis/easeclaw-api/revisions/79a190b20f61?raw)