A representative software team reviewing notes at a shared table, with no readable product interface

API

A predictable contract for business workflows

The reference, explorer, SDK maps, and examples come from the same operation catalog. Use the guide here to understand the integration model before opening exact endpoint details.

API behavior

Authentication

Use scoped API credentials or an approved OAuth flow. Credentials are owned by an organization.

API behavior

Acting-user context

Operations that affect user-owned records require an authorized user context.

API behavior

Pagination

List operations expose stable cursors so integrations can resume without offset drift.

API behavior

Idempotency

Mutation examples include an idempotency key so safe retries do not repeat side effects.

API behavior

Requests and errors

Request IDs, machine-readable failures, and rate-limit headers support troubleshooting.

API behavior

Sandbox

Sandbox credentials stay isolated from live organization data and calling providers.

curl -X POST "$CALLFORA_API/api/v1/click2dial" \
  -H "Authorization: Bearer $CALLFORA_API_KEY" \
  -H "X-Organization-Id: $ORGANIZATION_ID" \
  -H "X-User-Email: agent@example.com" \
  -H "Idempotency-Key: call_crm_1042" \
  -H "Content-Type: application/json" \
  -d '{"destination":"+1555010188"}'

Generated from voice.click2dial · success 200

Integration Hub API Explorer — Explorer executes the verified operation catalog against the selected environment.

Open exact API reference and OpenAPI

Build with Callfora

Scope the integration your team wants to build.

Let’s find the right way to connect your business.

Book a demo Start your workspace