API / Developer Terms
Terms for using the ZARZOOM developer API and integrations.
KEY DETAILS — the only place these values appear. To update the company, country, product, contact or date, change them here and nowhere else in this document.
Field Value Company ZARSK Ltd (referred to in this document as "the Company", "we", "us" or "our") Product / Service name ZARZOOM (the "Service") API base [API BASE URL, e.g. /api/v1] API documentation [OPENAPI / DOCS URL] Governing law England & Wales, United Kingdom Developer contact [DEVELOPER EMAIL] Last updated [DATE]
1. About these Terms
1.1 These API / Developer Terms govern your access to and use of our application programming interface, including any read and write endpoints, the OpenAPI specification, presigned upload flows, keys, tokens and documentation (together, the "API").
1.2 They form part of, and are incorporated into, our Terms of Service. Words defined in the Terms of Service have the same meaning here. Where these API Terms conflict with the Terms of Service on API matters, these API Terms prevail for those matters.
2. Access, keys and security
2.1 We may issue API keys, tokens or credentials ("Credentials"). Credentials are confidential and tied to your account and Workspace. You are responsible for all activity carried out using your Credentials.
2.2 You must keep Credentials secret, store them securely server-side, not embed them in client-side or public code, rotate them if compromised, and notify us promptly of any suspected compromise. We may rotate, suspend or revoke Credentials to protect the Service.
2.3 You must use the API only over secure connections and follow the security requirements in our documentation, including the use of idempotency keys where provided to avoid duplicate operations.
3. Acceptable use of the API
3.1 Your use of the API is subject to the Acceptable Use Policy and these Terms. In addition, you must not: (a) exceed, evade or manipulate rate limits, quotas or usage allowances; (b) use the API to build a product that replicates or competes with the Service, or to scrape or extract data beyond what the API is designed to return; (c) interfere with, overload, probe or attack the API or its infrastructure; (d) use the API to publish Content that breaches the Acceptable Use Policy, any law, or any Third-Party Platform's rules; or (e) misrepresent your application, or use the API in a way that could expose us or any Third-Party Platform to liability.
3.2 Publishing via the API is subject to the same risk allocation as the rest of the Service. Content you create, schedule, or publish through the API — including automated and unattended publishing — is published to your Connected Accounts as your own Content, at your own risk, exactly as set out in the Terms of Service. Automated API publishing carries the same risks as Auto-Publish.
4. Rate limits and quotas
4.1 The API is subject to rate limits and quotas described in our documentation (for example, workspace-scoped write limits). We may apply, change, or enforce limits to protect the Service. We may throttle, queue or reject requests that exceed limits, and you must handle such responses gracefully.
5. Changes to the API
5.1 We may change, deprecate or remove API endpoints, fields, versions and behaviour. Where a change is material and breaking, we will use reasonable efforts to give advance notice and, where practical, a transition period. You are responsible for keeping your integration up to date.
6. Your application and your end users
6.1 If you build an application on the API that is used by other people, you are responsible for that application, for your relationship with its users, for an appropriate privacy notice and lawful basis, and for ensuring your users comply with these Terms and the Acceptable Use Policy to the extent relevant. You must not present your application as operated or endorsed by us unless we have agreed in writing.
6.2 Where your application processes personal data through the API, the Data Processing Agreement applies between us, and you are responsible for your own controller obligations to your users.
7. Data and rights
7.1 Content and data you submit or retrieve through the API are governed by the ownership and licence provisions of the Terms of Service. We grant you only a limited, non-exclusive, revocable right to use the API in accordance with these Terms; we reserve all other rights in the API, its specification and documentation.
8. Disclaimers and liability
8.1 The API is provided "as is" and "as available". We do not warrant that it will be uninterrupted, error-free or backward-compatible. Our disclaimers and the limitation of liability in the Terms of Service apply to your use of the API, including the cap on our aggregate liability.
9. Suspension and termination
9.1 We may suspend or revoke API access immediately for breach of these Terms, the Acceptable Use Policy, security risk, excessive load, or where required by law or a Third-Party Platform. Your right to use the API ends when your subscription or these Terms end.
10. Language
10.1 The authoritative version of these Terms is the English version. Translations are provided for convenience only.
10.2 In the event of any conflict, inconsistency, ambiguity, or question of interpretation between the English version and any translation, the English version prevails.
End of API / Developer Terms.