Docs
Quickstart: your first three requests
Create an API key in the app, send it as a Bearer token, add a lead with POST /api/v1/leads/add, and list leads with GET /api/v1/leads. A lead needs a LinkedIn profile URL and the id of one of your connected LinkedIn accounts.
Published by Sellinger AI. Numbers and settings checked on 19 October 2026 against the fact register. Report an error.
1. Get a key
- Create the key from the API integration in the app. The raw key is shown once, so save it. A key looks like sk_live_ followed by 48 characters.
- A team can hold up to 5 active keys at once. Revoke one you no longer use.
- Send the key on every request as Authorization: Bearer sk_live_.... See authentication.
2. Find a LinkedIn account id
A lead created through v1 must belong to one of your connected LinkedIn accounts. Copy the account's id from the LinkedIn channel in the app. The API does not yet offer a v1 call that lists them.
3. Add a lead
curl -X POST https://app.sellinger.ai/api/v1/leads/add \
-H "Authorization: Bearer sk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"linkedin_profile_url": "https://www.linkedin.com/in/example-person",
"linkedin_account_id": "YOUR_ACCOUNT_UUID",
"full_name": "Example Person",
"lead_source": "api"
}'| Field | Required | Notes |
|---|---|---|
| linkedin_profile_url | Yes | Must look like https://linkedin.com/in/username |
| linkedin_account_id | Yes | A LinkedIn account that you own |
| agent_config_id | No | Filled in from the account when you leave it out |
| full_name, email, company_size, industry, location, notes | No | Text fields |
| status | No | One of the lead statuses, such as NEW |
| utm_source, utm_medium, utm_campaign | No | For attribution |
| conversation_history | No | A list of messages, each with sender (bot or lead), channel, message and an ISO timestamp |
4. List leads
curl "https://app.sellinger.ai/api/v1/leads?status=NEW&limit=50&offset=0" \ -H "Authorization: Bearer sk_live_YOUR_KEY"
Use GET /api/v1/leads/{id} for one lead and PATCH /api/v1/leads/{id} to update it.
Putting a lead into a campaign
The v1 add call does not take a campaign. The v2 MCP routes do: POST /api/v2/mcp/leads accepts an agent_id, and POST /api/v2/mcp/leads/bulk/assign takes lead_ids (up to 500) and an agent_id. A v2 lead needs at least an email, a LinkedIn URL or a phone number. If your key is not tied to a team, also send an x-team-id header.
Common questions
What happens if the lead already exists?
Can I try the API without a LinkedIn account?
Which base URL do I use?
Sources and method
Sellinger API code read on 19 October 2026. The in-app reference is at app.sellinger.ai/docs. No OpenAPI file exists yet.
Related: Authentication, Errors and limits, MCP connector.
