Getting started

Point your SMS provider’s base URL at smsyra in staging or CI, and use an smsyra API key (it starts with smy_) where your provider’s key goes. smsyra 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 smsyra one below, and its key for your smsyra 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 the code with the OTP API.

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

Guides by provider

All base URLs

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

More

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