Preflight an outbound call or SMS against the pre-dial gates, persisting nothing
Answers whether POST /v1/calls (or an SMS send) would be refused before dialling, without creating anything. For channel outbound_voice (the default) it asks both pre-dial questions a call meets, in the same order: first the workspace capabilities (destination country, channel, use-case profile, review signals, caps), then, only if those allow it, the per-call outbound policy (purpose, user_authorization with both authorized_by and reason, caller-number readiness, the destination format). stage says which question answered: outbound_authorization or outbound_policy. For any other channel (sms) only the capabilities question is asked. This is a preflight of those two gates, not a full admission: number rules, plan concurrency, maintenance windows and the wallet reservation are not evaluated; spend caps are checked only against the amount_minor you send, calling rules only when you send project_id, and caller-number readiness only when you send from_number_id (the call itself always needs one).
Request
- Base URL: https://api.skysay.ai
- URL: https://api.skysay.ai/v1/policies/authorize-outbound
- Auth: none declared
Request body
Response
The decision the first refusing gate gave, or allowed when both allow.
Changes
No recorded changes to this operation across all 1 revision of this API.