The changes made by Microsoft in October will also be applicable for the use of APIs (Application Processing Interfaces). The plans of the application programming interface, which serve as a kind of toolbox for developers, have been modified.
Increase in the limit of API requests
Users can now make a higher total number of API calls. These changes are applicable to Dynamics 365 applications, as well as Power Apps and Microsoft Flow.
Exceeding capacity utilization
The service limits are determined according to the normal usage patterns at 5-minute intervals and every 24 hours. Microsoft affirms that most users will not reach these limits.
Intensive cluster operations
For intensive grouped operations defined on a dedicated user, additional capacity may be required if the license capacity is systematically exceeded. A new SKU will be available to increase the capacity of API requests in increments of 10,000 calls per day.
Extension of license agreements for existing customers
If you were already a Dynamics 365 customer prior to October 1, 2019, your contract will be extended for a 12-month period as of now. Alternatively, it can be extended after the expiration of the current Dynamics 365 subscription period, depending on the longer duration. During this period, the new service limits mentioned above will not apply.
New add-ons when your usage is exceeded
Have you exceeded your usage? No problem. Power Apps and Microsoft Flow offer new add-ons which increase your daily API request limit in case of overflows.
What does an API request include?
Requests in the Microsoft Power Platform are different kinds of actions a user performs across a variety of products. At a higher level, below is what constitutes an API call:
Connectors – all API requests to Power Apps or Microsoft Flow connectors.
Microsoft Flow – all the steps of actions on Microsoft Flow
Common Data Service* – all CRUD operations, as well as special operations such as “share” or “assign”. These can be from any client or application and use any SOAP or REST terminal. These include (but are not limited to):
- asynchronous workflows
- customised checks carrying out the operations mentioned above.
* Note that for the Common Data Service, there will be a small set of internal system transactions that will be excluded. This is particularly the case with login and logout operations. As wellas with system metadata operations, such as getclientmetadata.
This concludes our article on the new developments of API requests. You will discover in our next article the new requirements for the new unified interface.
If you have any questions about this new transition, contact our team, who will be able to offer you personalized advice.