Reference

Seats, team and AI SDR

Everything on the app's Accounts page, Team settings and AI SDR settings. Changes need a Read + write key and are logged against the key that made them.

Last updated 22 October 2026

LinkedIn seats

GET/seats

Every seat with its status and health, limits, what it sent today, warm-up, Sales Navigator and any cooldown. The same data as the Accounts page.

Call	What it does
`PATCH /seats/{id}`	Change limits and warm-up (body on the right). Limits above the platform's safe ceilings are refused.
`DELETE /seats/{id}?confirm_name=…`	Disconnect the seat: it leaves every campaign and its login is removed. Cannot be undone. The seat's exact name must match, so a wrong id never disconnects a seat.
`POST /seats/{id}/reconnect-link`	A login link on connect.gelee.ai for the seat's owner to reconnect. Valid 15 minutes, and the seat lands back in this workspace.

PATCH body

weeklyobject

connections, messages, openProfiles, paidInmails, profileViews, companyViews, scrapes, comments, searchesMonthly.

warm_upboolean

Ramp a new or rested seat up slowly.

prioritystring

primary, standard or warmup.

New seats are added in the app, where your plan's seat count is checked.

curl -X PATCH "https://www.gelee.ai/api/v1/seats/SExF…" \
  -H "Authorization: Bearer gk_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "weekly": {
      "connections": 120,
      "messages": 300
    },
    "warm_up": true
  }'

AI SDR settings

GET/sdr

How the AI SDR replies: mode (approval or autopilot), knowledge base, objection answers (including ones it added itself), follow-ups, voice, ICP and filter sets. ?section= narrows it.

PATCH /sdr/{section}	Changes
`replies`	Reply mode (approval or autopilot) and reply rules.
`knowledge`	Add, change or remove knowledge-base entries.
`objections`	Objection answers, including auto-added ones.
`follow_ups`	The follow-up ladder.

The body is that section's input as GET /tools documents it (sdr_set_replies, sdr_set_knowledge, sdr_set_objections, sdr_set_followups).

curl "https://www.gelee.ai/api/v1/sdr?section=replies" \
  -H "Authorization: Bearer gk_your_key"

Teammates

POST/teamread_write

Body

actionstringrequired

invite, set_role or remove.

emailstringrequired

The teammate.

rolestring

admin, member, ambo or connector. The role decides what they can do in the app and the API.

Same rules as Settings, Team: owners cannot be removed or changed here.

curl -X POST "https://www.gelee.ai/api/v1/team" \
  -H "Authorization: Bearer gk_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "invite",
    "email": "sam@acme.com",
    "role": "member"
  }'

Every assistant tool over REST

POST/tools/{name}

GET /tools lists every tool the in-app assistant has that your key can call, each with its JSON input schema. POST /tools/{name} runs one with that JSON as the body. Use it for anything without a friendlier route: building sequences, AI variables, ICP, calendars and more.

The request is the go-ahead

In the app the assistant asks before it changes anything. On the API your request is the confirmation, so a change is applied in the same call. A read key sees read tools only, and tools that message people are marked needs_send.

curl -X POST "https://www.gelee.ai/api/v1/tools/campaign_edit" \
  -H "Authorization: Bearer gk_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "campaign_id": "9a2c…",
    "name": "Q4 Founders (EU)"
  }'