Skip to main content

​
Errors

The public BLIPS API already carries response examples for common failure cases across the OpenAPI document. That is enough for Mintlify to render endpoint-local error examples inside the generated reference.

​
Shared public error shape

Across the current public contract, error examples consistently follow this envelope:
  • status
  • code
  • message
  • details

​
What belongs in this page

This MDX page should stay focused on cross-endpoint guidance that does not fit naturally into one operation page:
  • how to read BLIPS error codes
  • which failures are retryable
  • which failures require operator action
  • how idempotency-related conflicts should be handled
  • how transaction-review conflicts differ from validation failures

​
What belongs in OpenAPI

Keep endpoint-specific examples in the OpenAPI spec:
  • status codes
  • response schemas
  • example bodies
  • operation-specific failure semantics
That split keeps Mintlify-generated endpoint pages accurate while this page stays concise and operational.