web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

OData REST API rate limit and throttling limit

(0) ShareShare
ReportReport
Posted on by 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)
  • Srinath Kannan Profile Picture
    on at
    RE: OData REST API rate limit and throttling limit

    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.

  • Verified answer
    Mea_ Profile Picture
    60,284 on at
    RE: OData REST API rate limit and throttling limit

    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

  • Verified answer
    Sergei Minozhenko Profile Picture
    23,093 on at
    RE: OData REST API rate limit and throttling limit

    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/.../)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Sohaib Cheema Profile Picture

Sohaib Cheema 764 User Group Leader

#2
Martin Dráb Profile Picture

Martin Dráb 619 Most Valuable Professional

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 603 Super User 2025 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans