Troubleshooting
Diagnose authentication failures, rate limits, stale data, MCP setup, and image issues against the Rewind API.
Most problems fall into a handful of buckets: a key the API does not accept, a window you have exhausted, a domain that has not synced recently, or an MCP client that has not picked up your configuration. Run the self-diagnostics first, then open the entry that matches what you see.
Self-diagnostics first
Two calls answer most questions. Run them before anything below:
curl https://api.rewind.rest/v1/health
curl -H "Authorization: Bearer rw_live_..." \
https://api.rewind.rest/v1/health/sync/v1/health confirms the API is reachable. /v1/health/sync reports each domain's last_sync, status, and error_rate, which separates a stale-data problem from an API outage (see sync health for the full response).
Requests and authentication
Data freshness
Claude and MCP
Images and the CDN
Error reference
Every error response uses the same { "error", "status" } envelope, where status matches the HTTP code.
| Status | Meaning | Common cause |
|---|---|---|
400 | Bad request | Malformed query parameter, invalid body, or unparseable input. |
401 | Unauthorized | Missing or non-Bearer rw_ header, unknown or revoked key, or expired key. |
403 | Forbidden | Authenticated, but the key lacks the required scope (read key on an admin endpoint). |
404 | Not found | The resource or route does not exist. |
429 | Too Many Requests | Rate limit exceeded; honor the Retry-After header. |
500 | Server error | Unexpected failure on the server. Retry, then report if it persists. |
Still stuck
If the self-diagnostics pass but the behavior is still wrong, open an issue at github.com/pdugan20/rewind/issues. Include the request URL, the response body, and the HTTP status code so the problem can be reproduced quickly.