Rate limit increase

Dear Zatca support team,

We are facing an issue where the number of invoices we are issuing is very big and we are being rate limited by Zatca clearance endpoint sometimes for a whole minute. This is making it so that invoices are piling up and soon there will be invoices that have been waiting for longer than 2 weeks to be reported due to the sheer volume.

Is there a way to increase the rate threshold for our service? We are already parallelizing our calls to Zatca API but it does not seem to help much since we are being rate-limited.

1 Like

In terms of numbers, it is taking around 30-40 minutes to clear 1,000 standard invoices.

this rate is good 1000 per 30-40 minutes …
i am not zatca team
my advice to u …is to distribute POS to more than one sending server
each sending server with its CCISD
I hope it helps

1 Like

Does ZATCA team share their rate limit / throttle policy? I can’t find it anywhere in documentation or in Q&A forum.

Unfortunately the current rate is not sufficient for our usecase, and I would like to hear from Zatca if it is possible to know the exact throttle policy to know if there is another way to do it than generate and manage multiple CCISDs.

Dear @malhamdan

Thanks for reaching out.

To ensure a comprehensive support, please provide the below info:

What is the avg size for invoices?
If you can share the full API requests and response to the SP mail.

Thanks.

Dear @idaoud , be advised that the issue is no longer occurring when we checked our systems today and the requests are being reported quickly with no issue. Thank you for your response and I wil be sure to provide these details if it were to happen again to SP email.

Dear @malhamdan

It’s great to hear that you are now able to send your invoices without any issues. However, if possible, could you please share the detailed information mentioned above? This will greatly aid us in our investigation and troubleshooting.

Thank you for your cooperation.

hi @idaoud

http-response something like “gateway timeout , 503 … ” at first attempt ( there is no fixed day or time ) and also its takes 30 seconds to 62 seconds

but its accepted at second http-request attempt …

Dear @asyed4u,

Thanks for reaching out, and welcome in our community.

Yes, it’s a known issue and our team working on it, will get back to you ASAP.

Additionally, if possible, could you please share the detailed information (Full request and response) to SP email?

This will greatly aid us in our investigation and troubleshooting.

Thank you for your cooperation, and welcome again in our community.