Documentation

Troubleshooting

Common error codes returned by the Meridian API and how to resolve them quickly.

401

Unauthorized

Your API key is missing, expired, or invalid. The server could not authenticate the request.

Resolution

Verify the Authorization header is present and formatted as Bearer <key>. Regenerate the key from the API Keys page if it has been revoked.

402

Payment Required

Your subscription has lapsed or the plan does not include the requested resource.

Resolution

Visit Pricing to upgrade or renew. If you believe this is a mistake, check that the correct license key is bound to your account under Billing.

429

Too Many Requests

You have exceeded the rate limit for your current plan tier.

Resolution

Implement exponential backoff with jitter in your client. TheRetry-After response header indicates how many seconds to wait. Consider batching requests or upgrading to a higher tier for increased throughput.

503

Service Unavailable

Meridian is temporarily overloaded or undergoing scheduled maintenance.

Resolution

Retry the request after the delay specified in the Retry-After header. Check status.getnimbus.net for live incident updates. Persistent 503s should be reported via the in-dashboard support widget.

504

Gateway Timeout

An upstream service failed to respond in time. This is usually transient.

Resolution

Wait at least 30 seconds before retrying. If the error persists for more than five minutes, open a ticket with the exact timestamp and request ID from the X-Request-Id response header. Avoid tight retry loops — they can prolong the outage.

Still stuck?

Our support team monitors the dashboard chat during business hours. Include the full error response body and request ID for faster triage.

Open a ticket