SMS Developer API Terms

These terms supplement the Silurian General Service Terms for the SMS Developer API.

1. Permitted messaging

The Customer may send lawful transactional, authentication and notification messages for its own services. Marketing or promotional traffic is permitted only where the Customer has a valid legal basis and complies with all consent, identification, quiet-hour and opt-out rules in every destination.

2. Recipient evidence and content

The Customer must maintain evidence of recipient permission where required, honour withdrawals promptly, and not send spam, phishing, fraud, malware, unlawful, discriminatory, harmful or misleading content. Purchased, scraped or randomly generated recipient lists are prohibited.

3. Sender identity

The Customer must use only sender names or numbers it is entitled to use. Carriers and authorities may require registration, verification, templates or local presence. Silurian may reject or replace an invalid sender identity and may request supporting evidence.

4. Credentials and rate controls

API credentials are confidential and must be stored securely, rotated after suspected compromise and restricted to authorised systems. The Customer must respect documented rate limits and must not evade traffic, destination or content controls.

5. Charging and delivery

Messages are charged according to the destination, segment count, encoding and current price shown by the service. Submission or an upstream acceptance is not a guarantee of handset delivery. Carriers can filter, delay, re-route or reject traffic and may return delayed or incomplete delivery receipts.

6. Monitoring and suspension

Silurian may process routing metadata and limited message information needed for delivery, fraud prevention, support, billing and legal compliance. Silurian may immediately restrict abusive, anomalous or unlawful traffic and cooperate with carriers and competent authorities as legally required.