What is this change about?
We are activating throttling (traffic limitation) on API calls towards 4human HRM. This means we are introducing clearer limits on how many API calls can be made, to ensure stable and predictable operation for all customers.
For this to work correctly, all custom-developed integrations must correctly identify themselves in each API call.
Who does this apply to?
This applies to customers with custom-developed integrations towards 4human HRM (for example internal systems, third-party integrations, or scripts).
What needs to be changed technically?
All API calls must include a custom header that identifies the customer instance.
Required header:
Shell
--header 'X-Api-Key: {instanceId}'
Show more lines
{instanceId} is replaced with your unique instance ID in 4human HRM.Why this is necessary
The header enables us to:
- identify traffic per customer instance
- apply the correct traffic limits (throttling)
- ensure stable, fair, and predictable integration
Calls without the correct
X-Api-Key may be limited or rejected when throttling is active.What IT or technical responsible should do
- Review all custom-developed integrations towards 4human HRM
- Verify that
X-Api-Keyis sent in the request header - Test the integrations after changes
Please take a look at this webinaret for more information on what and how to do this adjustment.
When must this be in place?
The change should be implemented before 1 June 2026.
For technical questions or clarification needs, contact 4human Support.
Comments
0 comments
Please sign in to leave a comment.