Symptom
Since release 2H2022, SAP has been working on implementing rate limits. These limits are still under development, and an official communication will be provided soon to explain how they will be applied.
Environment
SAP SuccessFactors HCM OData API
Resolution
1. As a general best practice, we would always advise customers to work with your API implementation team to reduce the number of API calls made per second. When in doubt, please reach out to SAP SuccessFactors Product Support at LOD-SF-INT-ODATA
2. What should I do if I have received a 429 – Too Many Requests error?
- Set your request to retry based on the recommended value, according Odata guide: Access Limits for OData V2
- If you are using Boomi or CPI to make the API call, no action will be needed, as both support http 429 and retry-after already.
NOTE: We always encourage our customers to review their usage of SAP SuccessFactors APIs and look for any optimization potential.
3. Does this change impact LMS APIs?
SAP SuccessFactors Learning OData APIs were already operating under API rate limits prior to this announcement and are not impacted. This announcement is specific to introducing rate limits to the rest of SAP SuccessFactors APIs. Please refer to the SAP SuccessFactors Learning OData APIs guide for more details
See Also
Guides:
In the Communities:
Best Practices:
Keywords
rate limit exceeded, RateLimitExceeded, the maximum allowed rate is, requests per minute, requests per second, throttling, API throttling, 40, 429, rate limiting, API-21198, INT-13843, SFS-209, SAP for Me, API Insights, usage , KBA , LOD-SF-INT , Integrations , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT-API , API & Adhoc API Framework , LOD-SF-INT-CPI , Standard SF to 3rd Party CPI (HCI) Content , LOD-SF-INT-BPI , Dell & Boomi Infrastructure , LOD-SF-INT-CE , Compound Employee API , LOD-SF-INT-CPI-TPI , Standard SF to 3rd Party Integration using CPI , How To
SAP Knowledge Base Article - Public