Overview
Every request to the BroadNet REST API carries your access token in an Authorization: Bearer header. The token is issued per account and comes from your BroadNet account; the API has no call that exchanges a username and password for a token. A missing or invalid token is rejected at the API gateway with HTTP 401 and a JSON body of two fields, error and message.
Legacy /websmpp credentials
The legacy HTTP API under /websmpp, kept for SMPP-era integrations, takes credentials as request parameters (user and pass, or accesskey) instead of a Bearer token. Use it only if you already depend on it; new integrations should use the Bearer-token REST API.
Examples
Copy, paste, replace the placeholders — these examples call the production API as written.
authenticated requestbash
curl -X POST https://api.broadnet.me/sms/identify \
-H "Authorization: Bearer $BROADNET_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "message": "Hello from BroadNet" }'401 Unauthorizedjson
{
"error": "Unauthorized",
"message": "Missing Authorization token"
}