Home/Docs
Developers
Every capability group is a GA service with a machine-readable OpenAPI spec. The catalogue below groups the real endpoints by capability; auth is a platform-standard SS-01 bearer token plus X-Tenant-Id, and money/usage writes carry an Idempotency-Key.
Auth & quickstart
# Auth: an SS-01 bearer token + your tenant header.
export TOKEN=... # from signup / an SS-05 Vault-backed API key
export TENANT=acme
# Select a least-cost carrier route for an outbound call (SS-40)
curl -X POST "https://api.brivas.io/api/v1/routes/select" \
-H "Authorization: Bearer $TOKEN" -H "X-Tenant-Id: $TENANT" \
-H "Content-Type: application/json" \
-d '{"destination":"+2348044550012","strategy":"least_cost"}'
# Send a governed message over the SMSC / OTT plane (SS-18)
curl -X POST "https://api.brivas.io/api/v1/send" \
-H "Authorization: Bearer $TOKEN" -H "X-Tenant-Id: $TENANT" \
-H "Idempotency-Key: $(uuidgen)" -H "Content-Type: application/json" \
-d '{"recipient":"+2348030001122","channel":"sms","body":"Hi from Brivas"}'
# Screen an A2P message for fraud on the same plane (SS-38)
curl -X POST "https://api.brivas.io/api/v1/voxguard/screen" \
-H "Authorization: Bearer $TOKEN" -H "X-Tenant-Id: $TENANT" \
-H "Content-Type: application/json" \
-d '{"sender":"BRIVAS","recipient":"+2348030001122","body":"..."}'No bespoke SDK is required — every endpoint is a plain HTTPS call with a bearer token. Generate a client from any service's openapi.json, or use curl as below. The same contract powers the platform's own console.
Endpoint catalogue
The catalogue is generated from the same capability data that drives the platform deep-dives — grouped by owning service, every entry a real endpoint from that service's OpenAPI contract.
services/routing/openapi.json · 55 endpoints shown · deep-dive →
services/vas/openapi.json · 38 endpoints shown · deep-dive →
services/notifications/openapi.json · 28 endpoints shown · deep-dive →
services/fraud/openapi.json · 26 endpoints shown · deep-dive →
services/mediation/openapi.json · 21 endpoints shown · deep-dive →
services/billing/openapi.json · 24 endpoints shown · deep-dive →
services/media/openapi.json · 21 endpoints shown · deep-dive →