KeelStack API

A read-only REST API over your sponsor pipeline, invoices, performance reports, and account activity. Pull KeelStack data into spreadsheets, Zapier, Make, n8n, your data warehouse, or any script.

Quickstart

1. Sign in and open Settings → API keys (Business plan).
2. Click Create key, name it after the integration you're building, and copy the key. It starts with ks_ and is shown exactly once — store it in your password manager or secrets store immediately.
3. Call any endpoint below with the key as a Bearer token.

curl https://keelstack.me/api/v1/me \
  -H "Authorization: Bearer ks_YOUR_KEY"

{
  "data": {
    "id": "usr_1a2b3c4d5e",
    "email": "you@yournewsletter.com",
    "name": "Alex Rivera",
    "brand_name": "The Weekly Deploy",
    "default_currency": "USD",
    "plan": "business",
    "plan_renews_at": "2026-10-01T00:00:00.000Z",
    "account_created_at": "2026-06-14T09:30:00.000Z",
    "docs": "/docs/api"
  }
}

Authentication

Every request carries your key in the Authorization header as a Bearer token:

Authorization: Bearer ks_YOUR_KEY

• Keys are scoped to your entire account — they see every sponsor, invoice, report, and activity event you can see.
• Keys are read-only. The API cannot create, update, or delete anything. There is no write-method surface in v1 by design: a leaked key can never corrupt your CRM.
• Your private sponsor notes are never exposed over the API — the notes field exists only in the dashboard.
• Revoke a key from Settings → API keys at any time; revocation is immediate.
• Treat keys like passwords. If one leaks, revoke it and create a new one — integrations using it stop at once.

Errors

Errors use a consistent JSON shape: { "error": string, "code"?: string }.

Rate limits

60 requests per minute per key. Every response includes these headers so well-behaved integrations can pace themselves:

Pagination

List endpoints use cursor pagination — stable under concurrent inserts, unlike page numbers.

# Page through every sponsor, 50 at a time
curl "https://keelstack.me/api/v1/sponsors?limit=50" -H "Authorization: Bearer ks_YOUR_KEY"
# → { data: [...], pagination: { has_more: true, next_cursor: "spn_9f8e7d6c" } }
curl "https://keelstack.me/api/v1/sponsors?limit=50&cursor=spn_9f8e7d6c" -H "Authorization: Bearer ks_YOUR_KEY"

Endpoints

Recipes

Post each new sponsor to Slack (Zapier)

1. Trigger: Zapier “Schedule by Zapier” every 15 minutes (Zapier has no native KeelStack trigger).
2. Action 1: “Webhooks by Zapier” GET to https://keelstack.me/api/v1/sponsors?limit=100 with your Bearer header.
3. Action 2: Filter created_at newer than the last run, then post each to Slack.

Weekly revenue snapshot (any runtime)

const BASE = 'https://keelstack.me/api/v1'
const key = process.env.KEELSTACK_API_KEY

const headers = { Authorization: `Bearer ${key}` }

async function* list(path) {
  let cursor = null
  do {
    const url = new URL(BASE + path)
    url.searchParams.set('limit', '100')
    if (cursor) url.searchParams.set('cursor', cursor)
    const res = await fetch(url, { headers })
    if (res.status === 429) {
      await new Promise(r => setTimeout(r, 1000 * Number(res.headers.get('Retry-After') ?? 5)))
      continue
    }
    if (!res.ok) throw new Error(`${path} failed: ${res.status} ${(await res.json()).error}`)
    const body = await res.json()
    yield* body.data
    cursor = body.pagination?.next_cursor ?? null
  } while (cursor)
}

let paidThisMonth = 0
for (const inv of list('/invoices?status=paid')) {
  if (new Date(inv.paid_at).getUTCMonth() === new Date().getUTCMonth()) {
    // Group by currency — records can differ from the account default.
    paidThisMonth += inv.amount // extend: bucket by inv.currency first
  }
}
console.log('Paid invoices this month:', paidThisMonth)

What the API deliberately does not do

• No writes. v1 is read-only end to end; the server rejects every non-GET request to /api/v1/* by construction. Write automation belongs in the dashboard.
• No private notes. The sponsor notes field is creator-private and never serialized by the API.
• No file downloads. Assets are listed as metadata; download files from the sponsor portal or dashboard.
• No cross-tenant access. Every query is scoped to the key's own account; other accounts' ids simply 404.

Changelog