Skip to main content
Organizations are the top-level container for every ThunderPhone resource — agents, phone numbers, calls, billing, and keys. An API key is bound to exactly one organization; the endpoints on this page are the handful that let you enumerate or manage the org resource itself. The dashboard lets a single user belong to multiple organizations and switch between them. The API treats your key’s bound org as implicit on every other page in this reference — you do not need an org id in URLs for resource operations. See Authentication for the full story.

​
Endpoints

MethodPathDescription
GET/v1/orgs/List organizations the caller belongs to
POST/v1/orgs/Create an organization
GET/v1/orgs/{id}/Retrieve a single organization
PATCH/v1/orgs/{id}/Update organization name
DELETE/v1/orgs/{id}/Delete the organization
GET/v1/webhookGet the single-URL webhook (see note below)
PUT / PATCH/v1/webhookSet the single-URL webhook

​
Organization object

{
  "id": 42,
  "name": "Acme Operations",
  "role": "owner",
  "created_at": "2026-04-20T18:24:10.113Z",
  "updated_at": "2026-04-20T18:24:10.113Z"
}
FieldTypeDescription
idintegerServer-assigned organization id
namestringDisplay name
rolestring | nullOn list responses, the caller’s role in this org (owner, admin, member)
created_attimestampISO 8601 in UTC
updated_attimestampISO 8601 in UTC

​
List organizations

Returns every organization the caller is a member of. 
curl https://api.thunderphone.com/v1/orgs/ \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY"
Response is a JSON array of Organization objects.
An API key is bound to exactly one organization, so this list almost always has a single entry when authenticated with sk_live_. The dashboard flow uses personal tokens and can return multiple orgs.

​
Create organization

curl -X POST https://api.thunderphone.com/v1/orgs/ \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "Acme Operations"}'
FieldTypeRequiredDescription
namestringyes1–120 characters
Returns 201 Created with the new Organization object. The creator becomes the owner member automatically.

​
Get organization

curl https://api.thunderphone.com/v1/orgs/42/ \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY"
Returns 200 OK with an Organization object, or 404 if the caller is not a member of the requested org.

​
Update organization

curl -X PATCH https://api.thunderphone.com/v1/orgs/42/ \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "Acme Ops"}'
Returns 200 OK with the updated Organization object.

​
Delete organization

Destructive and irreversible. Only allowed for the owner. You must remove all other members first. A user cannot delete their only organization.
curl -X DELETE https://api.thunderphone.com/v1/orgs/42/ \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY"
Returns 204 No Content.
StatusCondition
204Deleted
400Other members still present, or this is the caller’s only org
403Caller is not the owner

​
Legacy single-URL webhook

This is the original webhook config: one URL receives every event type (call.incoming, call.complete, …). It is still supported for existing integrations. New integrations should use the Webhook Endpoints system (multiple URLs, per-endpoint secrets, event filtering) — see Webhooks overview.

​
Get webhook config

curl https://api.thunderphone.com/v1/webhook \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY"
Returns 200 OK with the webhook row, or 404 if the org has not configured a webhook yet. 
{
  "url": "https://example.com/thunderphone-webhook",
  "secret": "whsec_abc123...",
  "created_at": "2026-04-20T18:24:10.113Z",
  "updated_at": "2026-04-20T18:24:10.113Z"
}

​
Set webhook URL

curl -X PUT https://api.thunderphone.com/v1/webhook \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/thunderphone-webhook"}'
FieldTypeRequiredDescription
urlstringyesHTTPS URL; http:// is allowed only for localhost during local dev
The secret is generated server-side and rotated only when you explicitly call PUT again. Store it in your secret manager and use it to verify the X-ThunderPhone-Signature HMAC on inbound payloads — see Webhooks overview.

Members

Manage roles and memberships within an organization.

Invites

Invite users to join your organization.

Webhooks

Subscribe to real-time events delivered as HTTP POST requests.

API Keys

Rotate the sk_live_ keys your integrations use.