# Debugging requests

> Reproduce failed requests and collect the details Cevoid support needs.

Breadcrumb: API › Debugging requests · Updated: 2026-10-17
Docs index: https://docs.cevoid.com/developers/llms.txt

When a request fails:

1. Verify the key with `/v2/me`.
2. Capture the response headers.
3. Record `Cevoid-Request-Id`.
4. Reproduce the request with a minimal curl command.

## Capture response headers

Use `curl -i` to include response headers:

```bash
curl -i "https://api.cevoid.com/v2/posts?limit=25" \
  -H "Authorization: Bearer ${CEVOID_API_KEY}"
```

Check these headers first:

- `Cevoid-Request-Id`: include this value when you ask Cevoid to investigate a request.
- `Cevoid-Processing-Ms`: compare server processing time with the total latency observed by your client.
- `RateLimit-*`: check whether the request was throttled.

## Verify authentication

If several endpoints fail, call `/v2/me` first. See [Authentication](https://docs.cevoid.com/developers/api/authentication.md) for the expected header and response.

If `/v2/me` succeeds, check the failed endpoint's path, parameters, and required scope.

## Reduce the request

Start with the endpoint and authentication only. Add one query parameter at a time, then add the pagination cursor last.

This isolates invalid parameters, resource IDs, and filters without changing several inputs at once.

See [Error handling](https://docs.cevoid.com/developers/api/errors.md#handle-errors-in-code) for a logging example.

## Escalate a request

Contact Cevoid support when the same request fails intermittently, returns an unexpected response, or still fails after you verify its parameters and scope.

Include:

- `Cevoid-Request-Id`
- the minimal curl command
- the full query string
- expected and actual behavior

Do not include the secret key.

---

Canonical: https://docs.cevoid.com/developers/api/debugging-requests