Skip to Content

IdentityCall API

The IdentityCall API lets you turn call recordings into structured, searchable, measurable data — transcription, speaker identification, emotion, goals, categories, summaries — and programmatically manage the projects, virtual numbers, and operators that produce those calls.

Start where you are

Quick Example

# Upload a recording (idempotent via external_id) curl -X POST "https://api.identitycall.ai/api/v1/public/recordings" \ -H "Authorization: Bearer $IDENTITYCALL_API_KEY" \ -F "file=@call-recording.mp3" \ -F "project_id=42" \ -F "external_id=crm-call-abc-123" \ -F "language=en" # Response includes public_id — use that in subsequent calls # {"data":{"public_id":"018f3a...","status":"pending", ...}} curl -X GET "https://api.identitycall.ai/api/v1/public/recordings/018f3a.../transcription" \ -H "Authorization: Bearer $IDENTITYCALL_API_KEY"

Base URL

All API requests should be made to:

https://api.identitycall.ai/api/v1/public

Authentication

All API endpoints require authentication via Bearer token:

Authorization: Bearer idc_your_api_key

API keys have one of two scopes:

  • Account-wide keys can see every project, operator, and virtual number in the account. They must include project_id when creating a recording.
  • Project-scoped keys are bound to a single project and can only read or write resources inside it.

Learn more about authentication →

Need Help?