Call actions endpoints removed from API reference

POST /call-actions, GET /call-actions, GET /call-actions/{id}, PUT /call-actions/{id}, and DELETE /call-actions/{id} are no longer part of the customer API surface and have been removed from the reference.

The routes remain in place for the dashboard, which uses cookie-session auth, but they were never reachable with a bearer API key. Any client that tried to call them with an API token received a 401. The API-ref section previously implied otherwise; that was incorrect.

Configure call-flow behavior through the agent config surface (/agent/{id} PATCH, and MCP configure_call_actions for end_call / transfer_call) instead.

Calls per second (CPS) — control how fast outbound calls start

You can now control how fast the platform starts your outbound calls, separately from how many run at once. Instead of sending requests slowly to protect your phone carrier, send everything in one go and tell us the rate your carrier accepts. Calls wait in the queue and start at exactly that rate. Nothing is dropped.

For numbers you import over SIP, org admins set the rate per SIP trunk on the Concurrency page. Every number on a trunk shares one rate, because that is where carriers enforce the limit. New trunks start at the safe default of 1 call/sec, and a change takes effect within about a second, including for calls already queued. Rented Smallest numbers are paced per provider by your plan.

New endpoints: GET /product/cps-limits and PATCH /product/custom-trunk/cps-limit.