Postman collection

Every endpoint, pre-configured — generated from the same OpenAPI spec as this documentation, so it never drifts.

Download Postman collection ↓

Set up in one minute

1. Import. In Postman: File → Import and drop the downloaded 23telecom-sms-api.postman_collection.json.

2. Set authentication. Open the collection → Variables tab:

   Variable	Value
   baseUrl	https://restlink23telecom.com/api/v1
   apiKey	Your key from the portal (Settings → API Keys)

3. Set idempotency before a send. Set idempotencyKey to a fresh value for this logical request, such as welcome-20260715-001. For Send SMS, enable the disabled Idempotency-Key header. Send individual SMS and the managed-activation Send one SMS from an integration request require the header and have it enabled already. Reuse a key only when retrying the exact same request body.

4. Send. Open SMS → Send SMS, replace the recipient with your own number in the example body, and hit Send.

Keep keys out of shared workspaces

Store apiKey as a current value (not initial value) so it never syncs to shared/team workspaces or exports. Treat the collection export as sensitive if a tool has embedded current values.

What’s inside

The collection mirrors the API structure: SMS (send, status), Messages (list, unified, CSV export), Statistics (aggregate, daily, by country), Account (balance, pricing) and Webhooks (settings, test, logs). Auth is handled at collection level — every request inherits the X-API-Key: {{apiKey}} header.

Alternatives

• API playground — try requests right in the browser, nothing to install.
• OpenAPI spec — import the raw spec into Insomnia, Bruno, Hoppscotch or your own tooling.