Connect API

The Connect API is the canonical external integration surface for RocketLead. Read leads and bookings, push leads from your CRM, check availability, and book calendar slots — all over standard HTTPS with a Bearer token.

Base URL

https://api.rocketlead.io/connect/...

Quick start

GET /connect/tables/
Authorization: Bearer rocketlead_live_<64-hex-secret>

For everything else — auth flow, error envelope, scopes — see Authentication & scopes.

Interactive API reference

The full Connect API is rendered as an interactive Scalar reference right here in the docs — every endpoint with schemas, parameter types, and a built-in “Try it” panel. Authenticate with your rocketlead_live_* token and execute requests against your real organization.

→ Open the reference

The OpenAPI spec itself is fetchable at /connect-spec.json on this site (or api.rocketlead.io/openapi/connect.json from the API server) — useful for code generation or piping into Insomnia, Bruno, or your own SDK pipeline.

What’s in this section

The pages here are conceptual companions to the interactive reference — they cover the patterns, gotchas, and cross-cutting semantics that don’t live in OpenAPI:

Concepts

• Authentication & scopes — token format, the three scopes, lifecycle, error codes.
• Merge patch (RFC 7396) — how PATCH applies partial updates.
• Automation triggers — which events fire from which Connect endpoint.
• Race conditions & idempotency — slot fills, duplicate creates, retry strategy.
• Workflows — common end-to-end patterns (CRM sync, booking-after-lead, reschedule).

Resources — slim per-resource pages with embedded schemas and differentiators:

• Leads — the table_entries resource.
• Bookings — calendar_bookings.
• Availability — slot search.
• Lookups — calendars, resources, appointment types, slots, blockers, mappings.

Things to know

Note

Connect operates on the same data as the console. A lead created via Connect appears immediately in the lead pool UI; a booking made via Connect shows up on the calendar instantly. There’s no separate sandbox.

Tip

Use the same automation triggers as the UI. Creating a lead via POST /connect/table_entries/ fires table.entry.added exactly as a console insert would — your automations run regardless of how the data lands. See Automation triggers.

Related

• Ingress webhooks — alternative inbound path when you don’t want to manage a Bearer token.
• Form widget — for embedding lead-capture forms instead of pushing leads programmatically.
• Guides — end-to-end integration recipes (fonio.ai, etc.).