Activation workflow
SMS API activation has no setup charge, but it is still recorded as a service order.
- Create or sign in to one Silurian identity and verify its mobile number.
- Add the usage plan to the V2 cart and confirm the client billing and tax profile.
- A zero-total order does not need a card payment.
- API credentials are created when invoicing and service setup are complete.
One activation per client
A client account with a pending, active or suspended SMS API product cannot order another activation. An in-progress activation order links back to checkout instead of creating a duplicate.
Transactional use
The API is designed for requested alerts, verification codes and operational customer updates. Sender identity, content and destination rules are reviewed before production use; unsolicited marketing is outside the intended setup.
Estimate, then submit
An estimate validates message and destination characteristics before sending. Accepted messages enter an asynchronous queue and return a stable reference; the HTTP response is not a delivery guarantee.
Delivery events
Callbacks can return delivery-state changes to the customer application. The receiver should verify requests, handle duplicate events idempotently and treat destination-network outcomes as external state.
Credentials and access
Use a separate revocable API token for each integration and keep it on the server. Optional source-IP restrictions can narrow where a token is accepted. Credentials must never be embedded in browser JavaScript.
Pricing
Public prices are per SMS part and exclude VAT. The authoritative estimate considers destination, encoding, number of message parts, enabled route and sender requirements before the application commits the send.