Authorize and check budget
POST/gate/authorize
A successful authorize creates or resolves an authorization lifecycle. Exact retries replay the accepted response before mutable policy or pricing state is reevaluated. Rejections before lease/admission state is committed are not pinned to the idempotency key. Advisory hints, including pricing.not_configured and estimated funding shortfalls, remain successful accepted outcomes. Estimated usage is never a funding admission limit. Billable prepaid traffic is denied when the authoritative current available balance, or a selected Budget's current headroom, cannot cover one quantity_minor at the feature's primary activity-meter rate. The threshold uses the current effective account price and rational ceiling. Postpaid and hybrid traffic may create fallback outstanding balance after rating.
Request
Responses
- 200
- 401
- 402
- 403
- 409
- 422
- 429
OK
Unauthorized
Admission was denied by a funding, quota, or Budget constraint. Funding denial is only possible for a billable prepaid request when the user's authoritative available balance is below the minimum funding for one quantity_minor at the effective primary activity-meter rate. The minimum is ceil(unit_price_xusd / unit_quantity_minor); an estimated request cost never causes denial. The stable code identifies the business constraint and hints provide safe, machine-readable remediation details. The rejected operation is not accepted or retained by idempotency and may be retried with the same key after the constraint is repaired.
Forbidden
Conflict
Unprocessable entity.
Too many requests (rate limited)