# 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**:

```json
{
  "code": 10001,
  "message": "Internal Server Error"
}
```

**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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.empe.io/develop/issuer/error-handling-and-troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.