AthanLab API Terms

These terms apply when you use the AthanLab Developer API ("the API") — the REST API at api.athanlab.com/api/v1 — with an API key. They add to our Terms of Service, Privacy Policy and Acceptable Use Policy, which also apply to everything you do through the API. Where they conflict about API use, these terms win.

"You" means the person or organisation that applied for API access — the AthanLab account that owns the API keys — and anyone using your API keys. Anything these terms do not cover, including who provides the AthanLab service and which law governs it, follows the Terms of Service.

You accept these terms when you apply for API access, and again when you create a key after we publish a new version (section 14). If you accept them on behalf of an organisation, you confirm that you are authorised to bind it. How the API works in detail is described in the API documentation.

• API access requires an application, and every application is reviewed by hand by the AthanLab team. We may approve or decline it at our discretion, and we tell you the decision by email. If we decline, the email says when you may apply again.
• Creating API keys and creating speech jobs require an active Max plan on the account that owns the keys. If the plan ends, your keys become read-only: you can still check jobs, download audio you already paid for, cancel jobs and read your usage. They create jobs again as soon as the account is back on the Max plan.
• The information in your application must be true. If what you use the API for changes materially from what you described, tell us at support@athanlab.com.

Everything you generate through the API is subject to the Acceptable Use Policy, exactly as if you made it in the app. In particular, you must not use the API to impersonate anyone, to deceive, defraud, harass or threaten anyone — including voice phishing, scam calls and fake customer-service calls — to spread disinformation, or to create content that is illegal where you or your listeners are.

You must not try to get around the API's limits, access controls or safety measures — for example by spreading requests over several accounts — and you must not scrape or reverse-engineer the API, probe it for security weaknesses or load-test it without our written permission.

• Use only voices you have the right to use: AthanLab's official voices; your own voice; a voice whose speaker has given you explicit, informed, written consent to create synthetic speech with it; or a marketplace voice, used within the marketplace rules of the Terms of Service.
• The voice cloning rules of the Acceptable Use Policyapply in full: never the voice of anyone under 18; a deceased person's voice only with the consent of their estate or legal representative; and a public figure's voice only with their documented written consent, whatever recordings of them exist.
• Never use the API to make audio that passes itself off as a real person saying something they did not say, without that person's consent.
• Where the law, or a platform you publish on, requires synthetic audio to be disclosed, you must disclose it — including to your own users.
• If a voice you use is reported as cloned without consent, we may remove it and pause your API access while we investigate.

• You are responsible for all text sent and all audio produced with your keys — including text your own users submit through your product. We do not pre-screen it.
• If your users can submit text or choose voices, your own terms must forbid the uses these terms forbid, and you must act promptly on misuse you learn about.
• If we tell you about abuse coming through your integration, you must help us stop it and, where we ask and the law allows, identify the user responsible on your side.

As in the app, you own the text you send and the audio generated from it (Terms of Service, section 7), subject to these terms and to the rights of anyone whose voice or words it contains. You may use that audio in your own products and pass it on to your users.

You give AthanLab the permission it needs to process, store and protect that content as these terms describe: to generate and deliver the audio, to fingerprint it and to investigate misuse. The API, its documentation, our official voices, models and software remain AthanLab's; these terms give you no rights in them beyond using the API as described here.

• Keep your API keys secret. Use them only from servers you control — never in a browser, a mobile app or a public code repository.
• Your keys are for you and your own systems. Do not sell, share or give them to anyone else, and never send a key to us — not even to support.
• You are responsible for all activity and all characters spent under your keys, including by someone who obtained a key you did not protect. An optional monthly budget on a key limits what that key can spend.
• If you suspect a key has leaked, revoke it in your dashboard at once, or rotate it without a grace period so the old secret stops working immediately, and tell us at support@athanlab.com. The grace period that keeps an old secret working after a rotation is for planned rotations, never for a leaked key.
• Keys expire at the end of the period you chose when you created them. We email you before a key expires.
• We may revoke a key we believe is exposed or misused, and we will tell you when we do.

The API has rate limits, concurrency limits and per-request limits, published in the documentation. We may change them, or set different limits for your account, to keep the service reliable for everyone. A request refused for a limit is not charged.

We may slow down, pause or suspend your API access or individual keys — without notice where there is urgent risk — if we reasonably believe you are breaking these terms, putting the service or other people at risk, or if your account is suspended. Where we can, we will tell you why and how to resolve it.

While your API access is suspended, every request made with your keys is refused, including checking jobs and downloading audio, and stored audio is still deleted on the schedule in section 9. If access is restored, keys we did not revoke work again.

• Input text and audio of each API job are kept for 30 days after the job is created, so you can download the audio and so we can investigate misuse, and are then deleted. Download what you need to keep. Authorised AthanLab staff may review them to investigate abuse reports, enforce our policies and provide support, as the Privacy Policy describes.
• For audio made through the API, this 30-day period replaces the Privacy Policy's general rule that generated audio is kept until you delete it.
• The job record — its id, status, character count, voice, format and the metadata you sent — is kept with your account for billing, support and audit after the text and audio are deleted. Do not put personal or sensitive information in metadata.
• Records of each API request — endpoint, status, timing, the key used and a pseudonymised client address, never your text or key secrets — are kept for up to 90 days for security and operations.
• Our Privacy Policy explains how we handle personal data. Only include personal information about other people in your text where you are allowed to share it with us for this purpose.

Every audio file generated through the API is fingerprinted and linked to the account and the API key that created it, like all audio made with AthanLab. The fingerprint is a cryptographic hash of the file: it does not alter the audio, and it is kept for audit after the audio is deleted, as the Acceptable Use Policy describes. We use fingerprints to trace misuse and to answer reports about specific audio.

• API jobs are paid from your AthanLab account's character balance — your Max plan's monthly allowance first, then Athan Tokens. One character through the API is one character in the app. There is no separate API bill.
• A job is charged the length of its text when it is accepted. A job that fails is refunded in full, automatically. A cancelled job stays charged only for the share already generated; the rest is refunded. Dry runs, idempotent replays and refused requests are free.
• Characters spent on a job that succeeded are not refunded automatically. If you believe a job was charged in error, contact support@athanlab.com with the job id.
• Plan fees, renewals and cancellation follow the Terms of Service.

• The API is provided "as is". There is no service level agreement: we do not promise that it will be uninterrupted, error-free or available at any particular time, or that a job will finish within any particular time, and we may pause it or make it read-only for maintenance. Failed jobs are refunded as section 11 describes.
• We may change the API. Within version 1 we make only additive changes; changes that could break a working integration are announced by email to key owners at least 90 days in advance, as the documentation describes.
• The limitation of liability in the Terms of Service applies to the API, and so does the indemnity in the Acceptable Use Policy — including for claims arising from audio your own users request through your product.

• You can stop at any time by revoking your keys in the dashboard.
• We may end your API access for a breach of these terms or of the policies they include, or end the API programme with reasonable notice by email.
• When access ends, your keys stop working. Stored text and audio are deleted on the schedule in section 9, so download what you need while your keys work.
• Scheduling your AthanLab account for deletion stops your keys immediately. Your API data is then handled like the rest of your account data, as the Privacy Policy describes.
• Sections 5, 6, 9, 10 and 12 continue to apply after your API access ends.

When we change these terms we publish the new version on this page with a new version date, and we tell key owners about material changes by email. You will be asked to accept the new version the next time you create an API key. Keys you already have keep working; continuing to use the API after a change takes effect means you accept it. If you do not accept a change, stop using the API and revoke your keys.

Questions about these terms, or reports of misuse coming through the API: support@athanlab.com. Never include an API key in an email.