Pardon our mess These API docs are a work in progress. Endpoints, examples, and behavior may change as we continue to develop the Partner API v2.

Partner API

Errors

Status codes, rate limits, and error payloads for Partner API v2.

Error envelope

{
  "success": false,
  "error": "Human-readable message"
}

Common status codes

StatusWhen
400Invalid parameters (bad dates, missing fields, unknown path_uuid, misconfigured calendar)
401Missing or invalid Bearer token; expired access tokens include code: "token_expired" (renew via POST /api/v2/auth/token/renew)
403Valid token missing the required scope
404Resource not found for this agency
409Conflict (for example a booking slot is no longer available)
429Rate limit exceeded

Rate limits

Limits are enforced per Partner API key (falling back to IP when no key identity is present), and are keyed by HTTP method + route pattern.

  • Most GET reads: 60 requests / minute
  • Typical writes (POST/PATCH/PUT/DELETE): 10–30 / minute depending on the route
  • Calendar bookings: 20 / minute
  • Money-sensitive ops (lead-order pause/cancel/patch, Voice AI cancel/wallet): stricter caps (about 5–30 / minute)
  • Token renew (POST /api/v2/auth/token/renew): 10 / minute per IP

Reduce parallel polling and cache availability or list responses where you can. See individual operation pages under Resources for endpoint details.

Example messages

  • Invalid or missing token
  • Token missing required scope: contacts
  • Invalid date range. Use YYYY-MM-DD for from and to.
  • Date range must be between 1 and 90 days inclusive.
  • first_name and last_name are required
  • phone is required
  • This time slot is no longer available.
  • Contact not found