Developers
API Documentation (Preview)
A preview of the planned AFU communication APIs for voice, messaging, verification and number masking.
Preview only. These endpoints illustrate the planned API design for AFU Voice API, which is a product concept. They are not live, and paths, fields and behaviour may change before launch. Do not use them in production code.
Authentication
Requests will be authenticated with an API key sent as a bearer token over HTTPS. Keys should be stored in server-side secrets and never embedded in browser or mobile code.
Planned endpoints
| Method | Path | Description |
|---|---|---|
| POST | /v1/calls | Create an outbound call |
| GET | /v1/calls/{id} | Retrieve call status |
| POST | /v1/messages | Send an SMS or WhatsApp message |
| POST | /v1/verify | Start an OTP verification |
| POST | /v1/verify/{id}/check | Check an OTP code |
| POST | /v1/masking/sessions | Create a number-masking session |
Example request
curl -X POST https://api.YOUR-AFU-API-DOMAIN.example/v1/messages \
-H "Authorization: Bearer $AFU_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"channel": "sms",
"to": "+91XXXXXXXXXX",
"template_id": "order_update",
"variables": { "order_id": "12345" }
}'
Webhooks
Status events such as call.completed, message.delivered and verify.approved will be sent to your HTTPS endpoint. Each request will include a signature header that your server should verify before trusting the payload.
Getting access
To join the early-access list or discuss an integration, request a demo or contact our team.
