Verinode Developer

Errors

One typed envelope, everywhere.

Every non-2xx response uses this shape:

{ "error": { "type": "authentication_error", "code": "invalid_api_key",
    "message": "Malformed API key.",
    "doc_url": "https://docs.verinode.ai/errors",
    "request_id": "req_…" } }

400	`invalid_request_error`: validation or missing fields.
401	`authentication_error`: missing, malformed, or revoked key.
402	`billing_error`: Intelligence Units exhausted.
403	`authorization_error`: missing scope or entitlement.
404	No such resource for this operator.
409	Conflict (e.g. an export already in progress).
422	Unprocessable (e.g. an event case that can't resolve).
429	`rate_limit_error`: includes `Retry-After`.
500	`api_error`: the request failed on our side. Nothing was returned, so never read it as an empty result — quote the `request_id` and retry.