SMS setup

Point your SMS provider’s base URL at Arqeno in staging or CI, and use an Arqeno API key (it starts with arq_) where your provider’s key goes. Arqeno answers in that provider’s own shape, keeps the text in your inbox, checks it against your DLT templates — and never sends it.

  1. Create a free workspace, then an API key on its API keys page. The key is shown once.
  2. Add your DLT templates: import your DLT portal’s export, or paste them one by one.
  3. In staging, swap your provider’s URL for the Arqeno one below, and its key for your Arqeno key.
  4. Send a text as usual. It appears in the inbox at once, Matched or Mismatched — with the first character that differs.
  5. In end-to-end tests, read back the code — or the whole text, links and all — with the test API.

Arqeno is for testing only: nothing is delivered to anyone, so never point production traffic at it.

Guides by provider

All base URLs

ProviderArqeno URLYour key goes in
AmazeSMShttps://api-arqeno.shriradhatechnologies.com/p/amazesms/api/smsthe key parameter
MSG91 (Flow v5)https://api-arqeno.shriradhatechnologies.com/p/msg91/api/v5/flowthe authkey header
Fast2SMShttps://api-arqeno.shriradhatechnologies.com/p/fast2sms/dev/bulkV2the authorization header
Twiliohttps://api-arqeno.shriradhatechnologies.com/p/twilio/2010-04-01/Accounts/YOUR_ACCOUNT_SID/Messages.jsonthe Basic-auth password (your account SID as the user)
Exotelhttps://api-arqeno.shriradhatechnologies.com/p/exotel/v1/Accounts/YOUR_ACCOUNT_SID/Sms/send.jsonthe Basic-auth password
Arqeno JSONhttps://api-arqeno.shriradhatechnologies.com/v1/messagesAuthorization: Bearer arq_…

More

  • DLT templates — exactly how a text is matched, and what Arqeno reports.
  • Failure modes — make a key answer with your provider’s errors, an outage or a slow answer.
  • Test API — read back codes, links or whole texts in tests, without a phone.