# Server errors

**HTTP status:** `500 Internal Server Error`

**Content-Type:** `application/problem+json`

**type:** `https://truescreen.redocly.app/errors/server-error`

This error is returned when an unexpected internal error occurs. The issue is not caused by the client request.

## Associated error codes

| Code | Detail | Example / notes |
|  --- | --- | --- |
| `TS-000` | Internal server error. | Generic unexpected error (`type`: `.../server-error`). |
| `TS-014` | Digital signature error. | See [Certification processing failure](#certification-processing-failure) below. (`type`: `.../server-error`) |


## Certification processing failure

This case is returned when certification **creation** succeeded but **asynchronous processing** did not complete successfully. It applies to **`GET /v1/certifications/{reportId}`** and to the **`webhook_url`** callback when processing ends in failure.

### Example response


```json
{
  "type": "https://truescreen.redocly.app/errors/server-error",
  "title": "Certification processing error",
  "status": 500,
  "detail": "Digital signature error.",
  "code": "TS-014"
}
```

### How to resolve

1. Treat the certification job as failed; do not expect a `200` completion payload for the same processing attempt.
2. If appropriate, **create a new certification** and monitor `GET` or the webhook again.
3. If the error persists, contact TrueScreen support with `code: TS-014` and the `reportId` from your integration logs.


## Example: internal server error (TS-000)


```json
{
  "type": "https://truescreen.redocly.app/errors/server-error",
  "title": "Internal server error",
  "status": 500,
  "detail": "Internal server error.",
  "code": "TS-000"
}
```

## Notes

- In extreme cases (e.g. API Gateway timeout, upstream error before the handler) the response may be a 5xx **with no** `application/problem+json` body: the client should also handle unstructured 5xx responses.
- If the error persists, contact TrueScreen support.