Skip to main content
Update organization-level spend caps, soft caps, and approval thresholds for PAYG usage
Audience: application and coding agent.

​
Canonical metadata

  • requestId
  • traceparent

​
Example request

curl -X PUT \
  -H "Authorization: Bearer $SECAPI_BEARER_TOKEN" \
  -H "secapi-version: 2026-03-19" \
  -H "content-type: application/json" \
  -d '{}' \
  "https://api.secapi.ai/v1/billing/budget"

​
Example response

{
  "requestId": "req_2ZK8Q1W9F4M6P7R3"
}

​
Give this prompt to your agent

​
Failure posture

  • treat non-2xx responses as contract-aware failures, not free-form errors
  • preserve requestId and traceparent in logs and downstream reports
  • if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff