Every Sozuri API call accepts the same small set of HTTP headers. Send your key in Authorization, describe your body with Content-Type, and you’re ready to go. Responses are always JSON.

Standard headers

Header Required Type Description
Authorization Yes, unless you send apiKey as a field String Bearer token containing your project’s API key, for example Bearer YOUR_API_KEY. Remember the single space between Bearer and the key. The project field is still required, in the body or the query string.

If you prefer, you can omit this header and pass apiKey inside the request body or the query string — see Authentication. A header named apiKey is not read.
Content-Type Yes, when the request has a body String Format of the request body. Use application/json for JSON payloads, or application/x-www-form-urlencoded for form submissions. A GET with query parameters needs no body and no Content-Type.
Accept No String Responses are always JSON, whatever you send here. application/json is a good value to send.

Example request

A typical authenticated POST looks like this:

POST /api/v1/messaging HTTP/1.1
Host: sozuri.net
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Accept: application/json

{
    "project": "Galaxion Marketing",
    "from": "MySenderID",
    "to": "254700000001",
    "message": "Hello, world.",
    "type": "transactional"
}

Response headers

Responses come back as Content-Type: application/json. Apart from a 401 or a 429, they also carry X-RateLimit-Limit and X-RateLimit-Remaining: your project’s allowance of API requests per minute, and how much of it is left. See Request rate.

Use cases

Quick reference for the most common header combinations.

JSON API call

Set Content-Type: application/json and Authorization: Bearer …, with project in the body. The cleanest choice for modern backends — the API key stays out of the body and URL.

Form-encoded request

If you’re posting from a legacy system that can’t build JSON, send application/x-www-form-urlencoded with the same fields and put apiKey in the body (or keep the Bearer header).

Quick GET test

For a one-off check from a browser or script, put project and apiKey in the query string. The key then appears in URLs and logs, so use the Bearer header in production.

Headers in hand. Send a message.

Try the Bulk SMS endpoint next, or grab a ready-made request from the code samples.