For the complete documentation index, see llms.txt. You can also append .md to any page URL to get its markdown version.
Skip to main content
For the complete documentation index, see llms.txt.

For the complete documentation index, see llms.txt

Error codes

When you make a request to Signicat's ReuseID API and there is an error, a response with an error object is returned.

If you have encountered an error, check the information on this page to investigate what might have caused the error and how to resolve it.

If you require assistance, you can contact us by creating a support ticket in the Signicat Dashboard.

Error object and generic error codes

In addition to these product-specific error codes, there are generic error codes which are applicable to all Signicat APIs.

To learn about these and how the error object looks, see our generic Error codes documentation.

MobileID error object​

For MobileID, the error object can be made up from the following 7 fields:

Example responses​

Example 1: MobileID response with error object
{
"type": "https://api.signicat.com/mobileid/core/openapi.json",
"title": "User entity does not exist",
"code": "user_entity_does_not_exist",
"status": 404,
"traceId": "4bf239c088089f2bca77d3a413909f1d",
"detail": "Failed fetching user with user ID : 90e1b3e5-93a7-458e-b42b-d1b57e65e26a and account ID : a-sdge-Abcdefghijk123456789."
}
What does this example mean?

In this example, we can determine that the user entity (referred to by the userId in the request) does not exist.

The detail describes which user ID and account ID this refers to, so that you can take action accordingly.

Example 2: MobileID response with failed validation of request parameters
{
    "type": "https://api.signicat.com/mobileid/core/openapi.json",
    "title": "Invalid request parameter",
    "code": "invalid_request_parameter",
    "status": 400,
    "traceId": "4bf239c088089f2bca77d3a413909f1d",
    "detail": "Your request body parameters have failed validation."
    "invalidParams": [
        {
            "name": "userId"
            "reason": "userId cannot be null or empty"
        },
        {
            "name": "deviceId"
            "reason": "deviceId cannot be null or empty"
        }
    ]
}
What does this example mean?

In this example, we can determine that multiple request parameters have failed the validation.

The invalidParams describes which request parameters have failed the validation, so that you can modify them to pass the validation.

MobileID error codes​

Generic errors

Some of the MobileID-specific errors listed on this page are generic and can describe a number of possible issues.

On this page