# `SERVER_ERROR` (HTTP 500): the request failed inside Spaw

Something went wrong on this side. The failure is logged against the request_id in the response, which is the fastest way for support to find it.

This is not a verdict about what you sent. A request that could not be understood answers 422, one asking for a record that is not there answers 404; this code means the request was fine and the server was not.

Unlike every other error, this one may have billed: a failure after the lookup ran but before the response was written leaves the credit spent. Check the balance on the usage page and quote the request_id if it does not look right.

**What to do.** Retry once — most causes are transient. If it repeats, write to support@spaw.co with the request_id and the endpoint, and check the status page for an open incident.

```json
{
    "success": false,
    "error": {
        "code": "SERVER_ERROR",
        "message": "Something went wrong on our side. Quote the request id if you get in touch.",
        "request_id": "req_01m1kgdm4xngzmbmff68g94w0c"
    }
}
```

Reference: https://spaw.co/docs/errors/SERVER_ERROR