Skip to main content
The Partner API is for reseller accounts only. A key from a regular Answering Agent team gets 401 on these endpoints. To read your own team’s conversations, tasks, contacts, and reports, use the Customer API.
The Partner API lets a reseller account:
  • Create and manage organizations for its customers.
  • Add users to those organizations with a role.
  • Provision phone numbers (locations) answered by the AI.
  • Embed the Answering Agent dashboard in its own app.
  • Give one partner login read-only dashboard access to several customer-owned organizations, with each owner’s approval.

How the accounts fit together

Your account in Answering Agent. You authenticate with an API key to manage all your customer organizations through the API.
Your customers’ businesses. provisioned organizations are owned by your partner account. linked organizations stay owned by existing Answering Agent customers. Partner writes to a linked organization are denied unless its owner or admin grants the narrow dashboard-viewer capability.
People who belong to organizations. Each organization has an owner, created with the organization, and can have more users. You identify users by your own system’s ID (external_id).
Phone numbers answered by the AI. Each location belongs to an organization and has its own phone number, settings, and AI configuration.
Your ID for a user in your system. It maps your users to Answering Agent users without exposing internal IDs.
Tokens that let you embed the Answering Agent dashboard. For multi-account viewers, issue a separate token for each organization_id. The iframe exchanges it for a short-lived bearer bound to that organization.

Base URL and authentication

The Partner API shares the Customer API’s base URL and header:
The key is the only credential. Requests are not signed, so keep the key on your server and treat it like a password. See Partner API authentication.

Typical integration flow

1

A customer signs up

A customer creates an account in your platform.
2

Create the organization

Your backend calls POST /organizations to create the organization and its owner.
3

Provision a phone number

Call POST /locations to provision a phone number for the customer.
4

Get an embed token

Call GET /users/{external_id}/embed-token.
5

Show the dashboard

Embed the Answering Agent dashboard in your app with the token. Your customer sees their calls, tasks, and reports.
The Partner API quickstart walks through each call with code.

Multi-account viewer flow

An account manager can use one login across several customer-owned organizations:
  1. Confirm each customer organization is linked and reports permissions.can_manage_dashboard_viewers: true.
  2. Create the partner-owned identity once.
  3. Attach its external_id to each approved organization with PUT /organizations/{organization_id}/dashboard-viewers/{external_id}.
  4. Request a token with the selected organization_id. Replace the embed iframe when you switch organizations.
  5. To remove access to one organization, detach that relationship. The identity and its other organizations stay as they are.
This access is read-only. It ends at once when the viewer relationship, the owner’s grant, the partner link, the membership, or the user is removed. See multi-organization dashboard viewers.

Example: onboard a customer

Partner API pages

Quickstart

Create an organization, a location, and an embed token.

Authentication

Create a key and send it with each request.

Organizations

Create and manage customer organizations.

Users

Manage users within organizations.

Locations

Provision phone numbers answered by the AI.

Embed the dashboard

Show the Answering Agent dashboard inside your app.

Get help