Skip to main content
The AlloMia API lets your software work with clinics that use AlloMia’s AI phone agents. Today you can:
  • Manage clinics (partner keys only): list, create, read, update and delete the clinics in your partner account, and sync each clinic’s metadata from your system.
  • Read calls: list a clinic’s calls, and get one call’s details, including its summary and links to the transcript and recording.
  • Place outbound calls: ask one of a clinic’s agents to call a phone number now, then check how the call ended.
  • Receive a callback: AlloMia sends a call.completed request to your URL when an outbound call you placed ends.
That is the whole API today. Agents, teams, knowledge bases, tools and phone numbers are set up in the AlloMia dashboard. There are no API endpoints for them. The API calls a clinic an organization and a partner account a tenant. This site uses “clinic” and “partner account” in prose, and the API’s own names for endpoints and fields.

Base URL

All endpoints are under:
Send requests over HTTPS. Request and response bodies are JSON, so send Content-Type: application/json with every body. Timestamps in responses are ISO 8601 strings in UTC, for example 2026-10-06T14:02:11.670Z.

Authentication

Every request needs an API key in the Authorization header: Authorization: Bearer sk-…. There are two kinds of keys. A clinic key works with one clinic’s calls and outbound calls. A partner key works across all the clinics in your partner account, and it is the only key that can manage clinics. Keys are created in the AlloMia dashboard by you or by the clinic, and some endpoints also check the role of the person who created the key. See Authentication.

Responses and errors

A successful request returns HTTP 200 with a JSON body. An error returns a 4xx or 5xx status and a JSON body with an error message. Some errors add details or code. The exact shape depends on the endpoint, so branch on the HTTP status, not on the message text. See Errors.

Limits

Make your first request

This example uses a clinic key to fetch the clinic’s most recent call.
1

Get a clinic key

In the AlloMia dashboard, someone in the clinic opens Organization Settings, then the API Keys tab, clicks Add Key, and copies the key from New API Key Created. See Create a clinic key.
2

Copy the clinic's organization ID

In Organization Settings, the Organization Information tab shows the Organization ID with a copy button. See Finding IDs.
3

List the latest call

A successful response looks like this:
If you get 401, check the key and the header format. If you get 404 with Organization not found, the organization ID doesn’t belong to the key’s clinic.

Where to go next

Authentication

The two kinds of keys, where to create them, and what each can call.

Errors

The error bodies each endpoint returns, and what to do.

Rate limits

Per-minute limits, the 429 response and its headers.

Finding IDs

Where to find organization, agent, phone number, call and outbound call IDs.

Organizations

Manage the clinics in your partner account and sync their metadata.

Calls

List a clinic’s calls and read call details.

Outbound calls

Ask an agent to call a phone number and check the result.

Call-completed callback

The request AlloMia sends to your URL when an outbound call ends.