BitelioBitelio

List SMS messages

Your project's SMS history, newest first, cursor-paginated — the same shape as GET /v1/emails, so one client pages both the same way.

Every row carries segments and encoding, and that is the point. SMS is billed per segment: a GSM-7 message splits every 160 characters, a Unicode one every 70. A single accented character in a template flips the whole message to Unicode and can double its cost. This is the only place that number is readable after the send.

The body is not in the listing — it is on GET /v1/sms/{id}.

GET
/v1/sms

Authorization

ApiKeyAuth

AuthorizationBearer <token>

API Key authentication. Secret keys (sk_*) are required for all endpoints except /v1/track. Public keys (pk_*) only work with the /v1/track endpoint for client-side event tracking. The project is automatically derived from the key.

In: header

Query Parameters

limit?integer

Page size.

Default25
Range1 <= value <= 100
cursor?string

The previous page's nextCursor. Opaque — return it verbatim.

status?string

Filter by delivery status.

Value in"PENDING" | "QUEUED" | "SENT" | "DELIVERED" | "UNDELIVERED" | "FAILED"
to?string

Destination in E.164, matched exactly.

since?string

ISO 8601.

Formatdate-time
until?string

ISO 8601.

Formatdate-time

Response Body

application/json

curl -X GET "https://api.bitelio.com/v1/sms"
{
  "data": [
    {
      "id": "string",
      "to": "string",
      "from": "string",
      "country": "string",
      "encoding": "GSM7",
      "segments": 0,
      "status": "PENDING",
      "error": "string"
    }
  ],
  "nextCursor": "string"
}
Empty
Empty