Last updated · May 2026
- Production-ready APIs
- SOC 2 Type I - In Progress
Errors
Every error_code DataVibe returns has a stable docs_url so you can hand a customer a single link instead of a stack trace.
How to read DataVibe errors
Every 4xx and 429 returned by Core or the dashboard proxy follows one envelope:
{
"error": {
"code": "RATE_LIMIT_EXCEEDED",
"message": "...",
"next_step": "wait",
"docs_url": "https://datavibe.cc/docs/errors/rate-limit-exceeded",
"retry_after_seconds": 30,
"request_id": "..."
}
}Always log the request_id; support uses it to trace the exact call across Core, worker, and any sink.
Catalog
- RATE_LIMIT_EXCEEDED — You've hit the per-key sliding-window rate limit.
- QUOTA_EXCEEDED / CREDIT_EVAL_*_LIMIT_EXCEEDED — Daily quota exhausted; upgrade or wait for the UTC midnight reset.
- VAULT_CHECKOUT_DISABLED — Vault checkout-lease API is disabled in this environment.
- WEBHOOK_HOST_NOT_ALLOWED — Destination host blocked by EGRESS_ALLOWED_DOMAINS or RFC1918 guard.
- SECRET_NOT_FOUND — No vault row for the requested workspace/kind/label.
- INVALID_OAUTH_STATE — OAuth state token did not match the originating request.
- ASSUME_ROLE_FAILED — STS AssumeRole call failed; check trust policy and external_id.
- REQUEST_ID_MISSING — Request id was not propagated; safe to retry once.