Errors
The values in the Message column reproduce the API response exactly.
General errors
Section titled “General errors”| HTTP status code | Message | Description |
|---|---|---|
| 400 | Bad Request | The request could not be completed or contains invalid information. Review the error details in the response. |
| 401 | Token is invalid | The access token is invalid or expired. |
| 401 | The | |
| 403 | Forbidden lead | The authenticated partner does not own the lead. |
| 500 | Internal Server Error | An internal application error occurred. |
Create lead errors
Section titled “Create lead errors”Review the endpoint documentation.
| HTTP status code | Message | Specific code | Description |
|---|---|---|---|
| 404 | Company doesn’t exists | 4046 | The credentials are not configured correctly. Contact your Creditas representative. |
| 404 | Auto not found | 4048 | The submitted |
Save personal information errors
Section titled “Save personal information errors”Review the endpoint documentation.
| HTTP status code | Message | Specific code | Description |
|---|---|---|---|
| 400 | This request can only be issued once | 40015 | This endpoint can be called only once per lead. |
| 409 | Existent lead | 4092 | A lead with the same RFC can request credit only once every 30 days. The |
| 412 | The RFC is not valid | 41219603 | The submitted RFC is invalid. |
| 412 | Rejected lead | 41217 | The application was rejected. The reasons are included in |
Financial information errors
Section titled “Financial information errors”Review the endpoint documentation.
| HTTP status code | Message | Specific code | Description |
|---|---|---|---|
| 412 | Rejected lead | 41217 | The application was rejected. The reasons are included in |
Address errors
Section titled “Address errors”Review the endpoint documentation.
| HTTP status code | Message | Specific code | Description |
|---|---|---|---|
| 400 | The entered neighborhood does not belong in that zipCode location | 40016 | The submitted neighborhood is not associated with the postal code. Review the postal code catalog. |
| 412 | Lead without personId | 4124 | The save personal information endpoint has not been called. |
Vehicle information errors
Section titled “Vehicle information errors”Review the endpoint documentation.
| HTTP status code | Message | Specific code | Description |
|---|---|---|---|
| 404 | Auto with id {{id}} not found | 4050 | The vehicle version identifier is invalid. Review the vehicle catalog endpoints. |
Send PIN errors
Section titled “Send PIN errors”Review the endpoint documentation.
| HTTP status code | Message | Specific code | Description |
|---|---|---|---|
| 400 | Channel is missing or incorrect | 400 | Allowed |
| 412 | Integration error | 400601 | The external PIN delivery services are unavailable. |
| 412 | Lead without personId | 4124 | Personal information is missing. Call the save personal information endpoint. |
Request offer errors
Section titled “Request offer errors”Review the endpoint documentation.
| HTTP status code | Message | Specific code | Description |
|---|---|---|---|
| 400 | The PINs are different | 400 | The |
| 400 | Missing necessary lead information | 40001 | The response lists the missing sections: personal, professional, or address information. Call the corresponding endpoint to provide them. |
| 403 | The PIN doesn’t match | 40301601 | The submitted PIN does not match the PIN sent to the applicant. |
| 404 | Lead not found | 4040 | The submitted |
| 404 | The user hasn’t requested a PIN | 404601 | A PIN has not been requested. Call send PIN first. |
| 412 | Lead without personId | 4124 | Personal information is missing. Call the save personal information endpoint. |
Update contact information errors
Section titled “Update contact information errors”Review the endpoint documentation.
| HTTP status code | Message | Specific code | Description |
|---|---|---|---|
| 404 | Lead not found | ||
| 400 | Bad request | The request format or content may be invalid. Review additionalInfo in the response. |
Postal code errors
Section titled “Postal code errors”Review the endpoint documentation.
| HTTP status code | Message | Specific code | Description |
|---|---|---|---|
| 404 | ZipCode not found | 4048 | The submitted postal code does not exist in COPOMEX |