API Terms

1. Who can use the API

You must have a SayIt account in good standing to generate an API key. Keys are personal to your account: usage over a key is billed against, and treated as authorized by, the account that created it.

2. Keeping your key secret

Treat an API key like a password. Do not commit it to a public repository, embed it in client-side code shipped to end users, or share it with anyone outside your organization. You are responsible for all activity under your keys, including credits spent, until you revoke them from Settings.

3. Credits and billing

API usage draws from the same credit balance as the web app — there is no separate API plan or subscription. Each action costs the same credits whether it's run from the web app, Telegram, or the API; see /api/v1/actions for current costs. Failed actions release their reserved credits back to you, same as elsewhere.

4. Rate limits and fair use

Each account can make up to 300 API requests per hour, across all its keys. Past that, requests get HTTP 429 until the hour is up.

We may also throttle, queue, or temporarily block requests that we reasonably believe are abusive, automated beyond normal integration use, or put the service at risk for other users. We'll aim to warn you first where practical, but may act immediately to protect the platform.

5. Acceptable use of the API

Do not use the API to build a product that resells raw access to it without adding your own material value, to circumvent the credit system, to scrape or bulk-extract data outside your own account, or for any purpose that would violate our main Terms of Service. Do not send us content you don't have the right to send, and do not attempt to reverse engineer the underlying models or prompts.

6. Your end users

If you integrate the API into your own app, you are responsible for your own end users: obtaining any consent they need to give for their content to be processed, handling your own customer support and billing relationship with them, and making sure your use of their data complies with the law that applies to you. We only have a relationship with you, the API account holder — not with your end users.

7. No guaranteed uptime or SLA

The API is provided on the same "as is" / "as available" basis as the rest of SayIt — see our Terms of Service. We do not currently offer a service-level agreement, uptime credits, or dedicated support response times for API access. Build in your own retry and error-handling logic.

8. Changes to the API

We may add, change, or remove endpoints, request/response shapes, or action ids as the product evolves. Where a change would break existing integrations, we'll make a reasonable effort to give notice, but cannot guarantee advance notice for every change, especially security fixes.

9. Suspension and revocation

We may revoke an individual API key or suspend API access for an account that breaches these terms, our main Terms of Service, or applicable law, without prior notice where we reasonably believe there's a risk to the service or other users.

10. Liability

Our liability for API use is subject to the same limits set out in our Terms of Service. We are not liable for how you use results returned by the API in your own product, or for decisions your end users make based on them.

11. Contact

Questions about integrating, or to report a security issue with the API? Email support@say-it.online.