Rate Limits

To prevent abuse of our service, we apply a general fair use policy with a shared rate limit of 300 requests per minute for xmatter.org. We might adjust this limit regularly to ensure that our service remains accessible to all users. We're looking for sponsors so that we can relax these limits for everyone.

For most use cases, you generally don't need to worry about rate limits. We design the API around typical access patterns with specialized endpoints to reduce read amplification. Because most reads are 404s, a prefix-indexed existence file allows clients to short-circuit early, only performing a full read when the key actually exists.

Caching

Cache-Control headers are set on all responses to ensure that clients and CDNs can cache responses appropriately. Most clients, proxy and CDNs will be able to automatically handle this for you. We do not recommend caching responses indefinitely, as this may lead to stale data.

CORS Preflight Requests

We will not enable CORS for the xmatter.org domain. You need to proxy requests through your own website/CDN. For Next.js projects, you can configure images.remotePatterns in next.config.js to allow image optimization and proxying.

Customized rate limits

Need customized rate limits for your use case we have "higher volume" APIs available. Contact us at <reveal email>.

Project Sponsors

We're looking for sponsors to help support our project and make it easier for everyone to use without worrying about rate limits.

Are you interested in sponsoring us? Contact us at <reveal email>.