SiteCall

For application developers

One workspace. Calls and texts.

SiteCall keeps the number, company details, routing, and carrier status together. Your application uses the same provisioning service as the SiteCall setup flow.

Authenticate and choose a company

Use a current SiteCall user access token in the Authorization bearer header. The user must be an owner or admin of the workspace in x-sitecall-workspace-id. An Atriam session or an OTP API key cannot authorize provisioning.

Create or sign in to a SiteCall account with a phone number or email, including a personal email. The SiteCall CLI and MCP client handle this login and retain the selected company for each command.

Read activation progress

GET https://sitecall.ai/api/v1/provisioning

The response includes the workspace ID, missing company fields, and separate voice and texting states for each assigned number. voice: configured means routing is configured; confirm an available device or forwarding destination and make a test call.

Provision in order

Download the JSON request and response schemas. These are generated from the API’s validators.

POST https://sitecall.ai/api/v1/provisioning accepts JSON commands with the same two authentication headers.

1. save_company_profile: send confirmed company facts once.
2. search_numbers: find an available local or toll-free number.
3. quote_number: get the exact company, number, monthly price, and expiring quote ID.
4. buy_number: submit the reviewed quote ID and matching number after authorization.
5. save_routing: choose the company’s inbox and call destination.
6. set_caller_name: list the name (up to 15 letters, numbers, or spaces) that call recipients see for a connected local number.
7. submit_toll_free or submit_dlc_identity: supply the actual messaging use and required verification information.
8. refresh_toll_free or verify_dlc_otp: complete the applicable carrier steps. Read activation progress again before enabling texts in your app.

Company registration and approval of another business do not activate this number’s texting. There is no paid company-lookup subscription in this flow. Phone numbers, usage, and carrier registration can have separate charges.

Handle retries safely

After a timeout, read activation progress and retry the same purchase quote. Do not order a replacement automatically. A successful purchase does not mean SMS is approved.

Errors return JSON with an HTTP status: 400 for invalid input, 401 for sign-in, 403 for permissions, and 409 for a state conflict. Oversized commands return 413. Results are never cached.

The current API uses user sessions. Unattended application credentials and automatic migration of existing Atriam numbers are not part of this release.