AtServiceTech

SMS API · GUIDE

List SMS DLT resources

Use the authenticated DLT Manager GET endpoints to list the DLT resources associated with the API key's workspace.

Available list endpoints

Each endpoint returns HTTP 200 with a data array containing only resources in the authenticated workspace. Authenticate with an active workspace API key.

  • Entities: GET /api/v1/sms/dlt/entities
  • Sender IDs: GET /api/v1/sms/dlt/senders
  • Content templates: GET /api/v1/sms/dlt/templates

Try it with your API key

Enter your workspace API key and optional filter values in the matching endpoint panel. Select Try it to send the GET request and view its response. The key is used only for the request and is not saved.

GET

Entities

/api/v1/sms/dlt/entities

The generated cURL command includes the API key you entered. Do not share it.

cURL Request
curl --request GET \
  --url 'https://atservicetech.com/api/v1/sms/dlt/entities' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Accept: application/json'
GET · HTTPS

Response

Enter a key and optional filters, then select Try it to see the response.

GET

Sender IDs

/api/v1/sms/dlt/senders

The generated cURL command includes the API key you entered. Do not share it.

cURL Request
curl --request GET \
  --url 'https://atservicetech.com/api/v1/sms/dlt/senders' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Accept: application/json'
GET · HTTPS

Response

Enter a key and optional filters, then select Try it to see the response.

GET

Content templates

/api/v1/sms/dlt/templates

The generated cURL command includes the API key you entered. Do not share it.

cURL Request
curl --request GET \
  --url 'https://atservicetech.com/api/v1/sms/dlt/templates' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Accept: application/json'
GET · HTTPS

Response

Enter a key and optional filters, then select Try it to see the response.

Example response

A successful list request returns a data array. Fields vary by resource type; this is a sample Entity response.

Example Sender ID response

The sender list uses the same data array and includes the linked Entity details.

Example Content Template response

The template list includes the saved message, linked senders, provider status, and Entity details.

Fields in other responses

Sender and template items include the linked Entity details. The API resolves each workspace link internally; requests use the registered numeric entity_id. An unfiltered list may return an empty data array when no resources have been added.

  • Sender IDs: senderId, status, createdAt, entity.
  • Content templates: templateId, message_id, senderIds, messageText, templateType, status, providerMessage, createdAt, entity.