#rfrisch_api

1 messages ยท Page 1 of 1 (latest)

covert oliveBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1334896690381197354

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

vagrant merlin
#

๐Ÿ‘‹ happy to help

analog tendon
#

good morning, thanks

vagrant merlin
covert oliveBOT
analog tendon
#

I dont think we are reaching that limit. However, im not sure how to check that.

We are using connect for our integration, is the limit per connected account or for all connected accounts together under our umbrella?

vagrant merlin
#

if you're getting a 429 HTTP response, which you are, this means that you are reaching that limit

#

the limit isn't per API endpoint

#

so it's not the number of invoices you send but all the API calls you do within a time frame

analog tendon
#

And it that across all connected accounts or by each invidual account, cause im looking at hte logs for the indvidual account and we are nowhere near 100 per second

vagrant merlin
analog tendon
#

ok, it seems as though it should be separate. Although, it explictly talks about read requets and and doesnt mention post requests so its unclear. Can you clarify?

visual walrus
#

In live mode it's still 100 read operations and 100 write operations

#

So a platform can do 100 read and 100 write on their own account and also 100 read and 100 write on each connect account

#

So they're separate buckets

analog tendon
#

thanks, looking at the logs for the account with the rate_limit error, we are well under the 100 requests per second limit so Im not sure why we are getting rate limited

visual walrus
#

They should be able to provide you more details