Skip to main content
Zeckta provides two ways to track delivery status:
  • Poll the Message Status endpoint
  • Configure a webhook callback URL
Webhook delivery is recommended for production applications because it provides real-time updates without polling.
A 202 Accepted response means Zeckta successfully accepted your request and queued it for processing.It does not mean the message has been delivered.Use the Message Status endpoint or Webhooks to monitor delivery progress.
Yes.Both single messages and campaigns support scheduling through the scheduledAt field.The scheduled timestamp must be in the future.
Use the Message Preview endpoint.The preview response includes:
  • Encoding type
  • Message length
  • Segment count
  • SMS units
  • Estimated cost
No message is sent during preview.
Messages may progress through the following lifecycle:
  • QUEUED
  • PROCESSING
  • SUBMITTED
  • SENT
  • DELIVERED
Possible failure outcomes include:
  • FAILED
  • UNDELIVERABLE
  • EXPIRED
  • REJECTED
Yes.Zeckta automatically detects message encoding and supports:
  • Arabic
  • Chinese
  • Japanese
  • Emoji
  • Accented characters
Unicode messages may consume more SMS segments than GSM-7 messages.
Yes.Use the Campaign API to send a message to multiple recipients in a single request.Campaign reports can be retrieved at any time using the Campaign Report endpoint.
A Sender Name (Sender ID) is the identifier displayed on a recipient’s device.Examples:
  • ZECKTA
  • MyShop
  • AcmeBank
Sender Names typically require approval before use.
Yes.Provide a callback URL when sending messages or campaigns.Zeckta will send webhook events such as:
  • MESSAGE_SUBMITTED
  • MESSAGE_SENT
  • MESSAGE_DELIVERED
  • MESSAGE_FAILED
  • MESSAGE_UNDELIVERABLE
  • MESSAGE_EXPIRED
  • MESSAGE_REJECTED
Yes.SMS messages, campaigns, sender names, and OTP sessions are isolated by workspace.A workspace cannot access resources belonging to another workspace.
The API returns:
429 Too Many Requests
Response headers include:
  • X-RateLimit-Limit
  • X-RateLimit-Remaining
  • X-RateLimit-Reset
  • Retry-After
Applications should respect the Retry-After header before retrying requests.