Symptom
API call timeevents give below error:
HTTP Response code as 429 (statusText: 'Too Many Requests') when the rate of requests to an API exceeds the application's capability
HTTP receiver adapter with an error "org.apache.camel.component.ahc.AhcOperationFailedException: HTTP operation failed invoking https://api-server> /rest/timemanagement/timeeventprocessing/clockinclockout/v1/timeevents with statusCode: 429".
Environment
- SAP SuccessFactors Time Tracking
- SAP SuccessFactors Time Tracking Clock in Clock out
Cause
The rate of requests to an API exceeds the application's capability
Resolution
There is a limit on the amount of API calls that can be made per day.
We provide batch provisioning of 1000 events together and allow only 300 such APIs in a day.
At the same time, the maximum number of time events for a user in a request should not exceed 200.
There is no way to extend these limits. Going over this limit generates the error: HTTP status code '429 - Too Many Requests'
| Operation Type | Limit | Notes |
| Query page size | 1000 | You can retrieve upto 1000 time events with every API call. |
| API Quota | 300 per day | You can make upto 300 API calls in a single day. |
| Rate limiter | 10 API calls per minute | You can make upto 10 API calls per minute at the rate of 1 API call for every 6 seconds. |
SAP Help page of SAP SuccessFactors API Reference Guide (OData V4) for clockinclockout
See Also
SAP Help page of Exporting Time Events
KBA 3205292 FAQ - Frequently Asked Questions regarding Import and Export of Time Events
KBA 3364562 The maximum number of time events for a user in a request should not be greater than 200
Keywords
https 429, HTTP status code 429, rate limit, too Many Requests, API limit, API exceed , KBA , LOD-SF-TTR-CIO , Clock In/ Clock Out , Problem
SAP Knowledge Base Article - Public