OData REST API rate limit and throttling limit

(0) Share

Report

Posted on by prasmadd123

145

We are implementing client for Dynamics 365 Finance and Supply Chain Management using OData REST API. We need OData REST API rate limit and throttling limit to handle it in our client implementation. We could not find it in Dynamics 365 Finance and Operations documentation.

Any inputs on API rate limit and throttling limit will help.

I have the same question (0)

All responses (3)

Answers (2)

Sort by

Verified answer

Sergei Minozhenko 23,095 on at

Like (0)

Report
Copy link

Link copied!

Hi Prasmadd123,

I think there are no rate or throttling limits itself on F&O side, at least I was able to push a couple of thousands request (3 entities with one record in separate changeset) with the rate of 4-5 requests per second in Tier1 environment. The only thing you need to keep in mind that oData requests could have lower priority than other sessions in case of heavy load on the system.

Also if you planning to use oData for mass operations (like 1000+ records per couple minutes), you could think about bundling and push data in a bigger chunk via Data package API, because of most likely oData pipe in one thread will not handle this amount of data in time.

But if you, for instance, are planning to use LogicApps connector there are throttling limits on the connector side (docs.microsoft.com/.../)

Was this reply helpful? Yes No
Verified answer

Mea_ 60,286 on at

Like (0)

Report
Copy link

Link copied!

There are no hard limits for OData but in documentation you can find recommendations and guidance regarding volumes and best API to handle them docs.microsoft.com/.../integration-overview

Was this reply helpful? Yes No
Srinath Kannan Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

You may find this article of interest: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/priority-based-throttling

OData/ Custom endpoints will trigger throttling events that will cause an HTTP 429 response to be sent with a Retry-After delay. We are recommending all customers to implement the response handler and manage the retry logic accordingly for all integration endpoints.

Was this reply helpful? Yes No