Errors

Hydracept uses HTTP status codes plus a stable public error envelope on failed control-plane calls.

Typical statuses

StatusMeaning
400Invalid request / policy rejection
401Missing or invalid Hydracept API key / session
402Budget exceeded
403Not allowed for this principal / project / environment
404Capability, job, or resource not found
409Conflict (including idempotency conflicts)
422Request validation failed
429Rate limited
503Provider unavailable

Envelope

Error bodies commonly include:

Do not parse provider-native error strings as the primary contract. Prefer Hydracept code values from the public OpenAPI and runtime responses.

Idempotency

Durable job submits accept idempotencyKey. Replaying the same key with a conflicting payload returns 409 rather than creating a second job.

Related