Extra terms for businesses and developers who send messages through the BalloAds API.
These terms apply on top of the Terms of Service when you use the BalloAds API, whether with a company API key from the web app or through the developer portal.
API keys
Keep your keys secret. Store them on your server, never in a mobile app, browser code or a public repository. Anything sent with your key is treated as sent by you and is charged to you.
A company can have up to 10 active keys. Revoke a key straight away if you think it has leaked, and create a new one.
Test keys are for building your integration. Messages sent with a test key are still delivered and charged.
Using the API
Everything you send through the API must follow the Acceptable Use Policy, including consent and opt-out rules. You are responsible for honouring opt-outs that reach you outside BalloAds.
Send only from your own company's sender IDs and sending addresses.
Do not use the API to test or attack our systems, to scrape data, or in a way that degrades the service for other customers.
We may set or change rate limits and will publish them in the API documentation. If your traffic risks the stability of the service, we may slow or pause it and will tell you why.
Developer portal accounts
If you build on BalloAds for your own clients, you are responsible for making sure each client's messages meet these terms and for having a lawful basis for their contacts' data. Credits bought in the developer portal do not expire; see the Billing and Credits Terms.
Changes to the API
We may add to the API at any time. We will give at least 30 days' notice before removing an endpoint or making a change that breaks existing integrations, unless a faster change is needed for security or legal reasons.
Suspending access
We may revoke a key or suspend API access if a key is compromised, if traffic breaks these terms or the Acceptable Use Policy, or if a network or regulator requires it.