URL Authorization
Authenticate requests with query parameters when header-based access is not practical.
Last updated · Markdown version
Bulkit also supports URL-based authentication for workflows where sending custom headers is difficult. However, using the Authorization: Bearer <your_api_key> header is strongly recommended.
Exact query parameter format
HTTP
?apikey=your_api_keyFor backward compatibility, query parameters also accept ?apikey=your_api_key&apisecret=your_api_secret or ?api_key=your_api_key.
Example
cURL / Bash
GET https://api.bulkitsms.com/api/v2/account/credits?apikey=bk_live_8n6JQv3K1h9Lp0MdWhen to use it
URL authorization can be useful for:
- simple command-line testing
- constrained tools or webhooks that do not support custom headers
- quick connectivity checks in internal tooling
Security caution
Avoid URL authorization in production whenever possible. Query parameters are more likely to be captured in logs, proxy traces, analytics tooling, and browser history.
Example requests
cURL / Bash
curl -X GET "https://api.bulkitsms.com/api/v2/account/credits?apikey=bk_live_8n6JQv3K1h9Lp0Md"