Common Integration Errors/Quirks
Teamtailor
Below is a table detailing common error codes returned by the Unified API, their meanings, and common remediation steps:
Error Code | Description | Probable Cause | Remediation Steps |
---|---|---|---|
501 | Bad Request | The API key is missing permissions to access the given endpoint | Ask your customer to re-authenticate following the steps outlined in the relevant documentation |
Hibob
Missing or inaccurate employment information
termination_date
may be missing or null as well asemployment_status
if theView selected employees' Lifecycle sections
is missing from the service user (refer to the Hibob guide for the full permission sets that your customer needs to enable)
Greenhouse
Error Code | Description | Probable Cause | Remediation Steps |
---|---|---|---|
404 | Not found | Greenhouse may also return 404 if an invalid Greenhouse user ID was provided in the on-behalf-of input in the account linking process. | Ask your customer to re-authenticate following the steps outlined in the relevant documentation |
SmartRecruiters
SmartRecruiters has restrictive rate limits and does not offer the ability of listing applications and interviews. This means a lot of requests need to be made to backfill this behaviour (and allow it in the unified API), combined with the rate limits it can take some time to list / sync applications & interviews.
Due to these behaviours, the interview
endpoint by default has a filter applied to only return interviews for candidates in the following status INTERVIEW
OFFERED
HIRED
TRANSFERRED
, filtering out candidates that are in REJECTED
WITHDRAWN
LEAD
and IN_REVIEW
status.
Lever
Error Code | Description | Probable Cause | Remediation Steps |
---|---|---|---|
400 | Invalid Request | This usually occurs because of a missing or malformed parameter. Check the documentation and the syntax of your request and try again. | Double-check the parameters you are sending (query parameters or body data) |
401 | Unauthorized | The credentials or scopes provided do not suffice to access this resource. | Verify the lever credentials in the integrations page per therelevant documentation |
403 | Forbidden | The Lever account settings don't authorize the oauth app to perform the requested operation. | Talk to a Super Admin on your Lever account to update your API settings. |
429 | Too many requests | Lever imposes a limit of the number of requests a client can make in a short time. Read more about our rate limiting here. | Implement a retry strategy (you can do this easily via retryConfig of the StackOne sdk ) |
500 | Server Error | There was an error on Lever or StackOne's end. | Contact StackOne via your dedicated slack channel or [email protected] |
503 | Service Unavailable | Lever is temporarily down for maintenance. Please retry your requests with exponential backoff. | Implement a retry strategy (you can do this easily via retryConfig of the StackOne sdk ) |
Updated 25 days ago