Tixly API Terms & Service

1. General Usage

Tixly provides a suite of APIs that enable integration with our ticketing and CRM services. By using these APIs, you agree to adhere to the terms outlined in this document. Any misuse of the APIs, including but not limited to excessive requests, unauthorized access, or attempts to bypass security measures, may result in the blocking or revocation of your API key.

2. API Rate Limits

To ensure fair usage and maintain system stability, we have implemented rate limits for our APIs. Different limits apply depending on the service in use. Below is an overview of the rate limits per API:

Tixly reserves the right to modify, introduce, or enforce additional rate limits as necessary to maintain system integrity and performance.

  1. Service Name

    1. Rate Limit

  2. eventapi

    1. 60 requests per 120 seconds
      • /v2/Events/,
      • /v2/EventsByCategory/
  3. crmapi

    1. No limit at the moment 
      • /v3,
      • /v3/events,
      • /v3/subscriptions
  4. posapi

    1. 10 requests per 60 seconds
      • /v2/auth/token,
      • /v2/customer/search
  5. adminapi

    1. No limit at the moment
      • /v1/admin/events

If your integration exceeds these limits or causes undue strain on our system, Tixly reserves the right to temporarily or permanently disable your API access.

3. Enforcement and Consequences

Failure to comply with these terms may lead to:

  • Temporary or permanent API key suspension.

  • Additional restrictions imposed on API usage.

  • Legal actions if misuse results in significant service disruptions.

4. Contact and Support

If you have any questions about these terms or need clarification on rate limits, please contact our support team for assistance.

By continuing to use Tixly’s APIs, you acknowledge and agree to these terms.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article