Skip to main content
The GoldRush Foundational API (REST) returns structured errors when something goes wrong. This page is the single reference for understanding error codes, handling rate limits, implementing retries, and debugging common issues.

Foundational API (REST) Errors

The Foundational API returns standard HTTP status codes along with a JSON error body. Example error responses:

Rate Limits

The Foundational API enforces rate limits based on your plan tier: Rate limits are enforced per API key and IP address. When you exceed your limit, you’ll receive a 429 Too Many Requests response. Back off and retry using the strategies below.

Retry Strategies

Exponential Backoff with Jitter

For transient errors (429, 500, 503), implement exponential backoff with random jitter to avoid thundering herd problems.

SDK Built-in Retries

The GoldRush TypeScript Client SDK handles retries and rate limiting automatically - no manual retry logic needed when using the SDK.

Debugging Tips

GoldRush API keys follow the pattern cqt_wF... or cqt_rQ... (26 base58 characters after the prefix). Double-check for trailing whitespace or truncation.
A 404 error often means the chain is unsupported. See Supported Chains for the full list.
Don’t rely on the HTTP status code alone. The JSON response body contains an error_message field with specific details about what went wrong.
Isolate issues from your application code by testing directly:
Track your API credit consumption on the GoldRush Platform dashboard to avoid unexpected 402 errors.
If you’re consistently hitting 500 or 503 errors, reach out to support@covalenthq.com with your API key prefix, the endpoint, and timestamps of the failures.

Quick Reference

Foundational API Auth

API key setup, authentication methods, and SDK usage.

FAQ

Common questions about plans, rate limits, and features.

Supported Chains

Full list of supported blockchains and endpoints.