#community-help

Rate Limit Issues for APIs on Typesense Cloud

TLDR Zildjian reports a rate limit issue but Kishore Nallan claims Typesense doesn't enforce rate limits. The issue seems associated with server-side API calls from nextjs.

Join the chat

Sep 05, 2023 (3 weeks ago)

Photo of md5-cbe120c5ccdca7b15a73bb4a03898b5e

Zildjian

07:54 AM

hello, we are having a rate limit issue, can we increase our rate limit to prevent this? This is not happening on our staging cluster

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

07:55 AM

We don't enforce a rate limit. What error are you getting?

Zildjian

07:56 AM

AxiosError: Request failed with status code 429

08:03

Zildjian

08:03 AM

it say's in the doc that if we need to increase the limit, we'll need to reach out to typesense support

Kishore Nallan

08:04 AM

Can you please point me to the section of the docs that talk about this?

Zildjian

08:04 AM

https://typesense.org/docs/cloud-management-api/v1/rate-limits.html

08:04

Zildjian

08:04 AM

> By default, each API Key you create can make a total of 30 requests per minute. If you need to have this limit increase, please reach out to support aT typesense dOt org.

Kishore Nallan

08:05 AM

Are you using the cloud management API to manage your clusters on Typesense Cloud? That limit only applies to the management API.

Zildjian

08:07 AM

oh, server api it is

Kishore Nallan

08:23 AM

We don't enforce any rate limits on the server API. If you are using a proxy to send the requests to Typesense Cloud, please check if that's running into limits.

Zildjian

08:26 AM

do you have a documentation regarding that?

Kishore Nallan

08:28 AM

Which API call produces this error?

Zildjian

08:28 AM

the search api

Kishore Nallan

08:28 AM

From the browser?

Zildjian

08:29 AM

we're using nextjs and on getStaticProps, we are calling that to build the page

08:29

Zildjian

08:29 AM

so we're calling it on the server side

Kishore Nallan

08:30 AM

Can you please post the actual response body for the 429 error?

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2779 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Optimizing Typesense Implementation for Large Collections

Oskar faced performance issues with his document collection in Typesense due to filter additions. Jason suggested trying a newer Typesense build and potentially partitioning the data into country-wise collections. They also discussed reducing network latency with CDN solutions.

8mo

Importing data to Typesense Cloud with JS client

Zaiste attempted to import data to Typesense Cloud but encountered an error. Kishore Nallan explained the error was due to server side backpressure and suggested a curl approach for the import.

23mo

Rate Limiting for Self-Hosted Typesense

David asked about rate limiting on self-hosted Typesense. Jason recommended using Cloudflare until Typesense introduces rate limiting.

Discussing Features for Typesense Cloud Dashboard

Stephano expressed the need for a Typesense Cloud dashboard to manage collections. Jason confirmed its development, also including features like editing and deleting items. James and Mica added comments about API key management and self-hosted Typesense compatibility.

30mo

Debugging Typesense API Key Error

James is getting an error related to the `x-typesense-api-key` header in their Typesense project. Harrison suggests passing the API key in the HTTP header, and Jason advises checking the key via curl and possibly closing a duplicate Typesense server.

21mo