Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions hyperfleet/standards/error-model.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
Status: Active
Owner: HyperFleet Platform Team
Last Updated: 2026-01-02
Last Updated: 2026-06-26
---

# HyperFleet Error Model and Codes Standard
Expand Down Expand Up @@ -110,9 +110,11 @@ HyperFleet APIs MUST return errors using the [RFC 9457](https://www.rfc-editor.o
| `type` | URI | Yes | URI reference identifying the problem type |
| `title` | string | Yes | Short, human-readable summary of the problem type |
| `status` | integer | Yes | HTTP status code (100-599) |
| `detail` | string | Yes | Human-readable explanation specific to this occurrence |
| `detail` | string | No | Human-readable explanation specific to this occurrence |
| `instance` | URI | No | URI reference identifying the specific occurrence |

> HyperFleet implementations SHOULD always populate `detail` to provide actionable context to API consumers. The field is schema-optional per [RFC 9457 Section 3.1](https://www.rfc-editor.org/rfc/rfc9457.html#section-3.1), but omitting it degrades the developer experience for partners consuming error responses.

### HyperFleet Extension Fields

In addition to RFC 9457 standard fields, HyperFleet errors include these extension fields:
Expand Down