UKG Pro offers both SOAP and REST APIs:
UKG Pro provides both SOAP-based and REST-based web services.
The UKG Pro API enables integration with UKG Pro data through these web service interfaces.
For REST APIs:
For SOAP APIs:
The API supports both JSON and XML formats for REST services.
UKG Pro provides a dual API approach, offering both SOAP and REST interfaces to access and integrate with UKG Pro data. This allows developers flexibility in choosing the API style that best fits their needs and existing systems. The REST APIs use modern authentication methods like Basic Auth and tokens, while the SOAP APIs follow SOAP 1.2 specifications. Both API types enable programmatic access to UKG Pro data for various integration scenarios.
Yes, the official UKG Pro API does have webhooks. UKG Webhooks allows you to subscribe to specific events and receive near real-time notifications when those events occur in your UKG Pro solution.
UKG Webhooks supports a wide range of events that you can subscribe to, including:
Employee-related events:
Document-related events:
Signature-related events:
Other HR-related events:
UKG Webhooks supports wildcards, allowing you to subscribe to a group of events from a specific event category.
Key features of UKG Webhooks include:
The benefits of using UKG Webhooks include:
To start using UKG Webhooks, you need to configure your webhook by specifying the callback URL, the events you want to subscribe to, and other relevant details. UKG Pro provides an API for creating and managing webhooks.
Here are the key points about the API Rate Limits for the UKG Pro API:
UKG Pro employs an API gateway to manage quotas and rate limits for API calls.
The rate limit is typically set for how many API calls a client can make over a 1 minute period.
If the rate of requests is too high, the server will return an HTTP 429 status code.
Receiving a 429 response is not an error, but a request to reduce the rate of API calls.
Applications should respect the 429 response and not try to circumvent it.
UKG is considering implementing a "Retry-after" header in the future with 429 responses.
Until then, a default delay of 1 second should be used before retrying after receiving a 429.
Optionally, an exponentially increasing delay can be used when retrying.
Do not attempt to bypass rate limits or spoof IP addresses.
Implement proper handling of 429 responses in your code.
Be prepared to add logic to check for and respect a "Retry-after" header in the future.
Consider using an exponential backoff strategy when retrying after rate limit errors.
In summary, the UKG Pro API implements rate limiting on a per-minute basis, returning 429 status codes when limits are exceeded. Proper handling of these responses is critical for applications integrating with the API. While specific numeric limits are not provided, the documentation emphasizes respecting the rate limits and implementing appropriate retry logic.
Based on the search results provided, here is the answer to your question about the most recent version of the UKG Pro API:
The search results do not explicitly state a specific version number for the most recent UKG Pro API. However, they do mention that the Pro 2024.R1 APIs are now available, which appears to be the latest release [2][3].
The UKG Pro API enables programmatic access to UKG Pro data via SOAP-based and REST-based web services [1].
UKG regularly updates their APIs with new features and enhancements. The most recent major update mentioned is the Pro 2024.R1 release [2][3].
The API specifications and version history can be found on the UKG Developer Hub website [1].
UKG provides both REST and SOAP APIs for different functionalities within the UKG Pro system [1].
Some of the recent updates and changes to the UKG Pro API include:
Introduction of UKG Webhooks, allowing subscription to specific events [3].
Addition of a full suite of Recruiting API resources and operations (over 100 in total) [3].
Enhancement of the Payroll Earnings Import resource [3].
Updates to the Employee New Hire API, including new fields for Iowa locations [3].
Introduction of a new top-level domain for the Universal Device Manager API [3].
Removal of the requirement for an AppKey in API calls [2].
Regularly check the UKG Developer Hub and the Version History for each API to stay updated on the latest changes and additions [2][3].
Use the provided API specifications to input appropriate authorization values and create example API requests [3].
Subscribe to the What's New RSS feed to receive updates about API changes and new features [3].
For any issues with API calls, check the UKG Pro status page in the UKG Community [3].
In conclusion, while there isn't a specific version number mentioned, the most recent version of the UKG Pro API appears to be associated with the Pro 2024.R1 release. It's recommended to refer to the official UKG Developer Hub for the most up-to-date information on API versions and changes.
To get a developer account for UKG Pro to create an API integration, you need to follow these steps:
First, you need to have access to UKG Pro as a customer. UKG Pro is an enterprise-level human capital management (HCM) system, so you or your organization must be a UKG Pro customer to access its API.
You'll need system administrator rights within your UKG Pro account. This is necessary to create and manage web service accounts.
UKG Pro APIs using Basic Authentication are only accessible with a web service account. To create one:
You'll need two API keys:
Once you have your account and API keys:
Based on the search results provided, here is a list of data models that can be interacted with using the UKG Pro API, along with what is possible for each:
It's important to note that the exact capabilities and data models available may depend on the specific permissions granted to the API user and the modules implemented by the organization using UKG Pro.