Developers

A REST API and signed webhooks.

Push leads in, manage campaigns and pull results out with the API, and react the moment a lead replies on any channel with webhooks. Included for every customer.

api.sh
$ curl -X POST https://app.graphkit.com/api/v1/campaigns/$CAMPAIGN_ID/leads \    -H "Authorization: Bearer gk_live_••••••••" \    -H "Idempotency-Key: import-0412" \    -d '{"leads":[{"profileUrl":"https://www.linkedin.com/in/hannah-scott"}]}'HTTP/1.1 201 Created{ "added": 1, "skipped": 0 } $ curl "https://app.graphkit.com/api/v1/leads?limit=2" -H "Authorization: Bearer gk_live_••••••••"HTTP/1.1 200 OK{ "data": [ { "id": "0193…a1", "name": "Hannah Scott" }, … ], "nextCursor": "…" }

REST API

JSON over HTTPS, cursor pagination, consistent errors and idempotency keys on every write.

MCP

GraphKit inside your AI assistant.

Everything GraphKit does is available as tools over MCP, so you can search leads, build campaigns and answer replies from Claude, ChatGPT or Cursor. Included for every customer.

Remote MCP server

Add GraphKit to your client with the URL and an API key from Settings, API keys.

  • Any MCP client

    Claude, ChatGPT, Cursor and other assistants that speak MCP over streamable HTTP.

  • Read or act

    A key with kit:read gets read-only tools; kit:write gets every tool, inside the key’s workspace.

  • Approvals

    Consequential actions never run straight away: they wait for a person to approve them in the app.

Webhooks and conventions

Predictable by design.

Signed webhooks

Each delivery is signed with your endpoint secret, retried with backoff up to 8 times, then kept as failed and listed in the app. Deduplicate on the event id. Payload shown is illustrative.

Errors and pagination

Every error has a snake_case code, a readable message and the matching HTTP status. Lists take limit and cursor.

Build on GraphKit.

API access, webhooks and MCP are included for every customer, at no extra cost.