Fair-Use Policy & Rate Limiting

Understand Prioticket’s API usage policies, rate thresholds, and how to stay within fair limits.

Prioticket APIs operate under a fair-use policy designed to ensure stable, scalable, and reliable integrations. While most partners won’t encounter strict limits under normal use, we do monitor usage patterns and apply targeted rate limiting where necessary to protect the platform and all connected systems.

What We Monitor

We continuously analyze API usage to identify:

• Incorrect or missing caching

• Inefficient chaining of API calls

• High error rates

• Excessive or unintentional traffic volumes

Our aim is to ensure every integration performs efficiently and does not negatively impact shared platform performance.

Rate Limiting Policies

We currently enforce two main limits:

1. 4XX Error-Based Rate Limit

To prevent repeated invalid or misconfigured requests, we enforce:

• 60 HTTP 4XX errors per minute, evaluated per client/IP

• If exceeded, the client will be temporarily blocked for 1 minute

• Applies to all 4XX error codes (e.g. 400, 404, 429)

This helps protect the platform from misbehaving or unstable integrations and encourages proper error handling.

2. Request Volume Limit

To prevent overload scenarios, we also enforce a general traffic threshold:

• Maximum 1000 requests per minute per IP address, evaluated over a rolling 1-minute window

• This limit does not include cached traffic, such as static content or availability data, which is typically cached under normal usage

Because most API calls (including content and availability endpoints) are cached, exceeding this threshold under normal conditions is very unlikely. This limit is designed to safeguard against edge cases and misconfigured loops.

If you believe your integration has legitimate reasons to operate at a higher frequency, or if you're approaching this threshold, please contact our API support team.

🛠️ This is not a system limitation, the platform can support higher volumes, but this is a sensible default per-integration safeguard.

DDoS Protection

We have robust DDoS mitigation systems in place at both the API and infrastructure level to protect against malicious attacks and sudden bursts of traffic.

Certification & Communication

During the API certification process, we provide guidance on efficient usage patterns and expectations. If we detect issues in live traffic, our team will proactively reach out with recommendations and assistance.

Need Help or Need a Higher Limit?

If you have questions about these limits, or if your integration requires an increased rate or different configuration, please reach out via the Prioticket API Support Service Desk.