Errors and Warnings

Most Common Errors

Error Code	HTTP Code	Description
missing_api_key	401	The x-api-key header is currently missing. Try again including the x-api-key header.
invalid_api_key	401	The API key is invalid. Try again with a valid API Key.
bad_request	422	The request was not valid, often due to missing a required parameter. Please, review your request and make sure all parameters are correct.
invalid_credentials	401	The login credentials provided are invalid. Please, ask the user to try again with valid credentials.
platform_unavailable	503	The platform is currently unavailable. Please, try again later or contact support.
too_many_requests	429	This is mostly common with the IMSS and ISSSTE platforms. We recommend you attempt to login with the user’s credentials the following day.
service_unavailable	503	The service is currently unavailable. Please, try again later or contact support.
request_timeout	504	The login failed due to a timeout. Please, try again later or contact support.
curp_has_inconsistencies	403	This error relates to the IMSS platform. The CURP is not valid or has inconsistencies. Please, ask the user to go to the closest IMSS's facility to resolve it.
platform_error	422	There was an error with the platform. Please, try again later or contact support.
invalid_otp	401	The OTP provided is invalid. Please, ask the user to try again with a valid OTP.
expired_otp	401	The OTP provided is expired. Please, ask the user to try again with a valid OTP.
email_not_validated	400	The email used is not validated. Please verify your email within the app to proceed. Once verified, you can try again.
invalid_phone_number	422	The phone number provided is invalid. Please, ask the user to try again with a valid phone number.
invalid_email	422	The phone number provided is invalid. Please, ask the user to try again with a email address.
lambda_error	503	There was an error with the platform. Please, try again later or contact support.
login_refused	400	This error is mostly common in Uber. It occurs when Uber blocks a login attempt. In this case, please ask the user to try to login again after 30 minutes.
invalid_otp_auth_key	401	There was an error with the platform. Please, try again later or contact support.
curp_not_found	404	The CURP was not found. Please, ask the user to go to their closest IMSS's facility to resolve it.
could_not_send_otp	401	There was an error sending the OTP code. Please, ask the user to try resending the OTP code again.
unable_to_get_performance	403	There was an error with the platform. Please, try again later or contact support.
recent_login_successful	412	The account successfully logged in less than 12 hours ago.
missing_social_security_number	403	The user does not have a social security number in IMSS's database. Please, ask the user to go to their closest IMSS's facility to resolve it.
social_security_number_mismatch	503	There appears to be a mismatch between the user's CURP and their social security number. Please, ask the user to go to their closest IMSS's facility to resolve it.
curp_not_in_platform	401	Verify that the CURP is correct. If the CURP is correct and you work in a department or entity affiliated with ISSSTE, go to the Human Resources area of your workplace to request that they verify your registration in the ISSSTE system.
nss_not_found_in_imss	404	The NSS was not found in IMSS. Please, ask the user to go to their closest IMSS's facility to resolve it.
invalid_nss	401	Invalid NSS status. Please, ask the user to go to their closest IMSS's facility to resolve it.
invalid_otp_session	401	There was an error with the platform. Please, try again later or contact support.
renapo_unavailable	400	The CURP was not found in Renapo. an error with the platform. Please ask the user to go to the nearest IMSS office to resolve it.

Common Warnings (Accounts)

A warning is triggered when a connection to an account was successful but there is some factor that prevents us from obtaining employment or income data. These warnings can be seen in the Palenca Console. For example:

The following table shows the most common warnings:

Warning	Platforms	Description
banned	Gig economy	The worker is banned from the platform.
not_registered	Gig economy	The worker is not registered on the platform.
curp_not_in_platform	IMSS and ISSSTE	The CURP is not registered on the platform.
zero_quoted_weeks	IMSS and ISSSTE	The worker does not have weeks ok work registered in IMSS.
rider_account	Gig economy	The user is registered as a rider, not as a driver in a Gig platform like Uber, Didi, Indriver, etc.
fleet_account	Gig Economy	The account belongs to a fleet. Due to this, data cannot be obtained.