API Terms

Last updated: 22/05/2026

These API Terms govern access to and use of Trac APIs.

1. Scope

These terms apply to any customer, Integration Partner, developer, or authorised user accessing Trac APIs.

API access is also subject to the applicable agreement, order form, documentation, data scopes, and technical controls.

2. API access

API access is provided under a limited, revocable, non-exclusive, non-transferable licence.

Caterlytix may approve, refuse, suspend, restrict, or revoke API access where necessary to protect Trac, comply with law, manage third-party obligations, or enforce applicable terms.

3. Authentication

Users must authenticate using approved methods.

API keys, tokens, credentials, and secrets must be:

• kept confidential;
• securely stored;
• not shared with unauthorised parties;
• rotated or revoked where compromised or no longer required.

4. Data scopes

API access is limited to authorised data scopes.

Users must not request, access, process, or store data outside the agreed purpose or authorised scope.

5. Usage limits

API use is subject to rate limits, request limits, technical constraints, and any applicable Fair Usage Policy.

Caterlytix may monitor usage and may throttle, suspend, or restrict access where usage exceeds agreed thresholds or creates risk to platform performance, security, availability, or compliance.

6. Technical requirements

Users must:

• follow API documentation;
• maintain compatibility with supported API versions;
• implement required changes within a reasonable timeframe;
• use current authentication and security mechanisms;
• handle errors, retries, and rate limits responsibly.

7. Restrictions

Users must not:

• bypass access controls;
• conceal their identity;
• interfere with consent or authorisation mechanisms;
• scrape or bulk extract data without permission;
• use APIs to build competing infrastructure;
• conduct unauthorised security testing;
• overload, disrupt, or degrade Trac.

8. Third-party systems

API functionality may depend on third-party systems.

Users must comply with third-party system requirements, including data permissions, rate limits, API changes, technical restrictions, and contractual obligations.

Caterlytix is not responsible for API disruption caused by third-party systems.

9. Changes to APIs

Caterlytix may update, modify, replace, or deprecate APIs from time to time.

Where reasonably practicable, Caterlytix will provide notice of material changes.

10. Suspension

Caterlytix may suspend API access immediately where there is misuse, excessive use, security risk, breach of terms, non-payment, or third-party requirement.

11. Liability

API use is at the user’s own risk and subject to the liability limits in the applicable agreement.

‍