Skip to content
RelationsAI
Getting started

API availability

Preview

API v1 is in private preview. This page lists what you can do through the API today, what is done in the console and what is planned, so you can design your integration around what exists.

Availability labels

These labels appear throughout the docs:

  • Available works in API v1 and is not expected to change incompatibly. During the private preview your workspace still has to be enabled to use it.
  • Preview works in API v1 for workspaces in the preview; details may still change before general availability. Changes are announced in the changelog.
  • Test mode works with test keys against simulated data.
  • Console only done in the RelationsAI console, not through the API.
  • Planned on the roadmap, not available yet.

Every operation works in both test mode and live mode, with the differences described in Test mode.

Available in v1

Every operation of API v1, grouped as in the API reference:

Workspace

Agents

Phone numbers

Calls

Campaigns

Contacts

Do-not-call list

Webhook endpoints

The event types delivered by webhooks are listed on the Event types page: call.ended, call.settled, campaign.started, campaign.paused, campaign.resumed, campaign.stopped, campaign.completed, campaign.failed and webhook_endpoint.test.

Console only

Console only These are done in the RelationsAI console:

  • Creating, configuring, testing and publishing agents, and switching them on or off.
  • Adding phone numbers and assigning them to agents.
  • Creating, rotating and revoking API keys (see API keys).
  • Members, roles, billing, balance and spend limits.
  • Workspace settings: calling hours, consent policy, security settings such as the IP allowlist, and custom field definitions for contacts.

Not offered in v1

The workspace object reports these as capabilities, so your code can check instead of discovering them from errors. Today each is false:

CapabilityWhat false means
agent_editingAgents cannot be created or edited through the API. Planned
call_ringing_statusCalls go from queued straight to in_progress or ended; there is no separate ringing status.
live_transcriptTranscripts are available after the call ends, not during it.
sentiment_analysisAnalysis has a summary, extracted fields and the goal outcome, without sentiment.
end_callA call in progress cannot be hung up through the API.
inbound_callsInbound calls do not appear in the call list.

webhooks says whether webhook delivery, a separate private preview switched on for the platform as a whole, is available: when it is false, endpoints cannot be created, test events and retries answer webhooks_not_enabled, and no events are sent. Read the capabilities with GET/workspace.

Planned

Planned Creating, configuring and publishing agents through the API. Until then, agents are a console prerequisite: build and publish them in the console, then use them from the API.

Nothing else is announced. New capabilities are added to the changelog when they ship.

Getting access

During the private preview, the API is enabled per workspace. A workspace that is not enabled answers every authenticated request with api_access_not_enabled (problems with the path, the body or the key are still reported first), and the platform's Settings → API Keys tab shows a preview notice instead of key creation. To request access, email support@relationsai.com from an owner or admin account, with your workspace name and what you plan to build.