SupportLog InSign Up
DocumentationAPIs & IntegrationsChangelog

Circleback

Integrate your application with the Circleback API

🚀 Quickstart

Connect to Circleback with Tenklo and see data flow in 2 minutes.

Create the integration

In Tenklo (free signup), go to Integrations -> Configure New Integration -> Circleback.

Authorize Circleback

Go to Connections -> Add Test Connection -> Authorize, then enter your API key. Later, you'll let your users do the same directly from your app.

Call the Circleback API

Let's make your first request to the Circleback API (list meetings). Replace the placeholders below with your Environment API key, integration ID, and connection ID:

curl "https://api.tenklo.dev/proxy/meetings" \
  -H "Authorization: Bearer <NANGO-API-KEY>" \
  -H "Provider-Config-Key: <INTEGRATION-ID>" \
  -H "Connection-Id: <CONNECTION-ID>"

Or fetch credentials with the Node SDK or API.

✅ You're connected! Check the Logs tab in Tenklo to inspect requests.

Implement Tenklo in your app

Follow our Auth implementation guide to integrate Tenklo in your app.

To obtain your own production credentials, follow the connect guide linked below.

📚 Circleback integration guides

Tenklo maintained guides for common use cases.

Official docs: Circleback API docs

🧩 Pre-built syncs & actions for Circleback

Explore Nango-provided actions in your dashboard. Extend and customize them to fit your needs.

No pre-built syncs or actions available yet.

Not seeing the integration you need? Build your own independently.

🚨 API Gotchas

  • Circleback API keys are personal: a key reads the meetings of the Circleback user who created it (ownership=Mine by default; All also includes meetings shared with that user). There is no workspace-wide key that reads other users' meetings.
  • List endpoints return a bare JSON array and paginate with an opaque cursor query parameter advertised in the RFC 8288 Link response header (rel="next"); page size is fixed server-side and there is no server-side updated-after filter.
  • Rate limits apply per Circleback account across all keys and OAuth tokens (Free: 3 requests/second and 20/minute; paid plans: 20/second and 300/minute); on a 429, wait for the Retry-After value before retrying.
  • GET /meeting/{meetingId} returns 404 for both missing and inaccessible meeting IDs.

Circle.so

Previous Page

Circleback (MCP)

Next Page

On this page

🚀 Quickstart📚 Circleback integration guides🧩 Pre-built syncs & actions for Circleback🚨 API Gotchas