How can i avoid retching the rate limit?

There's two options. First, you could indeed download the whole dataset of shows and store it locally using the show index endpoint: https://www.tvmaze.com/api#show-index

Alternatively, consider the following:

We say at least, because rate limiting takes place on the backend but not on the edge cache. So if your client is only requesting common/popular endpoints like shows or episodes(as opposed to more unique endpoints like searches or embedding), you're likely to never hit the limit. For an optimal throughput, simply let your client back off for a few seconds when it receives a 429.

So if you're only accessing common endpoints like /shows/1, /shows/2, /shows/3 etc, you could implement an HTTP client that automatically pauses for a few seconds when it receives a HTTP 429 status code from our API, then automatically retries that request before moving on to the next one in the queue.

@david wrote:
There's two options. First, you could indeed download the whole dataset of shows and store it locally using the show index endpoint: https://www.tvmaze.com/api#show-index

Alternatively, consider the following:

So if you're only accessing common endpoints like /shows/1, /shows/2, /shows/3 etc, you could implement an HTTP client that automatically pauses for a few seconds when it receives a HTTP 429 status code from our API, then automatically retries that request before moving on to the next one in the queue.

ok, nice

So this means that requesting https://api.tvmaze.com/search/shows?q=girls 60+ times will most likely give me 429-status

but requesting https://api.tvmaze.com/shows/139 etc. 60+ time will be ok?

@4456465 wrote:
ok, nice

So this means that requesting https://api.tvmaze.com/search/shows?q=girls 60+ times will most likely give me 429-status

but requesting https://api.tvmaze.com/shows/139 etc. 60+ time will be ok?

You'll most likely be OK. There's still a chance that you're unlucky enough to request 60 shows that don't exist in the edge cache. If you go for this route, I would encourage you to properly handle HTTP 429's either way to prevent random errors at some point in the future.

@david wrote:
You'll most likely be OK. There's still a chance that you're unlucky enough to request 60 shows that don't exist in the edge cache. If you go for this route, I would encourage you to properly handle HTTP 429's either way so prevent random errors at some point in the future.

Ok. Thanks. ill probably do it in the https://api.tvmaze.com/shows/139 way then
 

Any good recommendations on how to handle this in JavaScript Vue3?

An if statement that checks 429 and shows the user "Sorry, try again in half a minute"?
 

And maybe having my TVMaze username in the HTTP header since it says: 

"While not required, we strongly recommend setting your client's HTTP User Agent to something that'll uniquely describe it. This allows us to identify your application in case of problems, or to proactively reach out to you.""

@4456465 wrote:
Any good recommendations on how to handle this in JavaScript Vue3?

An if statement that checks 429 and shows the user "Sorry, try again in half a minute"?

No, what I meant is that your code would automatically retry the request after a few seconds when we return a 429. You could look at something like https://www.npmjs.com/package/fetch-retry to accomplish that.

@david wrote:
No, what I meant is that your code would automatically retry the request after a few seconds when we return a 429. You could look at something like https://www.npmjs.com/package/fetch-retry to accomplish that.

Ah, ok. Any particully timelimit? Im afraid of beeing banned:)

@4456465 wrote:
Ah, ok. Any particully timelimit? Im afraid of beeing banned:)

I'd suggest an exponential backoff. For example, something like retry #1 after one second, retry #2 ater two seconds, retry #3 after four seconds, etc.