This guide includes general error messages you might encounter while testing or configuring an integration, as well as UKG-specific errors that may appear when running API calls (e.g., via Postman or a similar tool).
🔐 401 – Unauthorized
Common Causes:
Username and/or password in Integration Manager are incorrect
Extra spaces (before/after) in the credentials
Password was changed in the ATS but not updated in IM
The ATS is submitting incorrect credentials
The user submitting the request lacks permissions in the ATS
🚫 403 – Forbidden
Common Causes:
Authorization credentials are valid, but the requesting system has not granted access to the resource
Missing permission scopes, roles, or REST API rights in the source system (e.g., UKG)
❓ 404 – Resource Not Found
Common Causes:
A referenced resource (package, location, applicant ID) is missing or invalid
The resource was removed or renamed after the order was submitted
⏱️ 408 – Timeout
Common Causes:
The webhook URL provided for status updates failed to respond in time
✅ Try:
Re-completing one of the non-instant searches in the report to re-trigger the status update.
💥 500 – Internal Server Error
Common Causes:
Duplicate package or location mappings in Integration Manager
Package is expired or inactive
An Accounting Bar is in place
Client profile is not enabled in deverus Admin
SwiftHire Mobile is not enabled or improperly configured
A field is passing
nullwhen it requires a valid value (e.g., Integer, String, Boolean)
🔎 API Testing Errors (UKG Ready)
If you're testing field index values using Postman or cURL, you may see these:
📄 “You do not have access to this saved report.”
Solution:
Have the HR client ensure the API user (e.g., precisecheck) has permission to view the Saved Report ID in UKG.
🔒 “Export Format is not allowed by security settings.”
Solution:
In UKG:
Go to Reports → Export Reports → Set Export Format to All Types
🚫 “403 Forbidden” on GET Applicant
Solution:
In REST API Resources, ensure the API user has:
✅ View Applicants
✅ Edit Applicants
✅ See All Applicants
❗ Bearer Token Error – “Couldn’t resolve address”
Solution:
Check the Host Name field in Integration Manager. It should contain only the base domain (e.g., secure4.saashr.com)
Do not include https:// or additional paths.
❌ GET Applicant returns no Custom Fields
Solution:
Ask the client to select or enter values for all four custom fields on the test applicant. Placeholder values are fine (e.g., "Submitted", "Report", "Message", "Standard").
🔎 7061 – “Could not find saved settings for Id”
Solution:
Double-check that the Report ID is correct. Ask the UKG contact to verify.
🔐 Account Locked
Solution:
If the account was locked due to failed login attempts, the UKG admin must unlock it and reset the password. Enter the new password into Integration Manager.