> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revolv3.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Request IDs

> Read the Revolv3 request id from every API response, and optionally send your own id so support can find the same call.

Every API response includes a Revolv3 request id in the `Request-Id` header. That id is how support finds one call, including a call that failed or timed out before an invoice or payment id exists.

These headers are the same on every endpoint.

## Response headers

| Header | When it is present | What it contains |
| - | - | - |
| `Request-Id` | Every response, including success | The id Revolv3 assigned to this call. Copy it when you contact support. |
| `Client-Request-Id` | Only when your request sent a valid `Client-Request-Id` | The same value you sent. |
| `X-ERROR-ID` | Error responses | The same value as `Request-Id`. Existing integrations can keep reading it. New integrations should read `Request-Id`. |

```http theme={null}
HTTP/1.1 200 OK
Request-Id: 4bf92f3577b34da6a3ce929d0e0e4736
Client-Request-Id: order-12345
```

## Send your own id

Add an optional `Client-Request-Id` request header when you want to match this call in your logs.

Use a value you already store, such as an order id or a GUID. A valid value is 1 to 128 characters and may contain letters, digits, and `.` `_` `:` `-`. A value made up only of 13 to 19 digits is ignored, so it cannot look like a card number.

Examples: `order-12345`, `3f2b8c1e-9d4a-4e7b-a1c5-6b0d2e8f7a91`, `checkout:2026-11-02.17`, `retry_1.order-12345`.

An invalid value does not fail the call. Revolv3 ignores it and does not echo it. Send one value only. Do not put card numbers, bank account numbers, or other sensitive data in this header.

The API does not read `X-CORRELATION-ID`. Use `Client-Request-Id`.

## Error body

Success responses do not add these ids to the JSON body. An error response includes `serverRequestId`. That field is the same value as the `Request-Id` header. When you sent a valid client id, the body also includes `clientRequestId`.

```json theme={null}
{
  "message": "One or more validation failed.",
  "serverRequestId": "4bf92f3577b34da6a3ce929d0e0e4736",
  "clientRequestId": "order-12345"
}
```

Other error fields are described in [API Response Codes](https://docs.revolv3.com/docs/error-codes/error-responses.md).

## What to send support

If you received a response, include `Request-Id`. On an error, `serverRequestId` and `X-ERROR-ID` are that same id.

Also include:

* `Client-Request-Id`, when you sent one
* the time of the call
* sandbox or production
* the request path
* the error body, with secrets removed

If the call timed out and you never received a response, there is no `Request-Id`. Send the `Client-Request-Id` you generated, the time, and the environment.

Log in to the Revolv3 portal and use the **help icon** to contact support.

## Related

* [Authentication](https://docs.revolv3.com/docs/authentication-security/merchant-access-token.md) — required request headers
* [API Response Codes](https://docs.revolv3.com/docs/error-codes/error-responses.md) — HTTP status codes and error bodies


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.