Error Handling and Troubleshooting

The Issuer Service uses standard HTTP status codes and JSON error responses:

Common Status Codes:

  • 400 Bad Request: Invalid request parameters or missing fields.

  • 401 Unauthorized: Invalid or missing x-client-secret or bearer token.

  • 403 Forbidden: Access denied to the requested resource.

  • 404 Not Found: Non-existent schema, credential, or offering ID.

  • 500 Internal Server Error: Unexpected server issues.

Example Error Response:

{
  "message": "Invalid request parameters",
  "value": "invalid_request",
  "code": 400
}

Troubleshooting Tips:

  • Validate request payloads against schema definitions.

  • Ensure correct and unexpired x-client-secret and bearer tokens.

  • Check logs for detailed error messages.

  • Verify stable integration with the EMPE Blockchain.

If issues persist, consider reviewing configuration, schemas, and network connectivity.

PreviousSecurity ConsiderationsNextFuture Enhancements

Last updated