Getting started

Arqeno stands in for your messaging providers in staging and CI. Point your app at it instead of the real provider, keep your code as it is, and every message is answered like the provider would, kept in a live inbox, checked — and never delivered to anyone.

Choose your channel

The same four steps on every channel

  1. Create a free workspace, then an API key on its API keys page. The key starts with arq_, is shown once, and works for every channel.
  2. In staging, change your provider’s base URL (or, for email, the SMTP host) to Arqeno’s, and use the Arqeno key where the provider’s key goes. Each provider’s guide says exactly what to change.
  3. Send as usual. Arqeno answers in the provider’s own shape, and the message appears in its inbox at once — SMS checked against your DLT templates, email with its code, links and checks.
  4. In end-to-end tests, read the code, the link or the whole message back with the test API — one call for SMS and email.

For every channel

  • Test API — wait for the newest SMS or email and get its code; list and read messages; delivery events.
  • Failure modes — make a key answer like the provider being down, erroring or slow.

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