@metreeca/tile
    Preparing search index...

    Interface Fault

    A fault raised against an interface.

    Problem details, as any consumer of Problem reads them, plus an identity for the occurrence they describe. The same issue raised twice gives two faults, told apart by instance, so a reader may clear either one on its own.

    RFC 9457 - Problem Details for HTTP APIs

    interface Fault {
        type?: string;
        status?: number;
        title?: string;
        detail?: string;
        report?: Value;
        instance: string;
    }

    Hierarchy

    Index
    type? status? title? detail? report? instance
    type?: string

    URI reference identifying the problem type.

    "about:blank"
    status?: number

    HTTP status code generated by the origin server.

    title?: string

    Short, human-readable summary of the problem type.

    Should be the same for all occurrences of this problem type, for example Payment Required or Not Found.

    detail?: string

    Human-readable explanation specific to this occurrence of the problem.

    report?: Value

    Machine-readable details about this occurrence of the problem.

    An RFC 9457 extension member, shaped as the reporting party requires, for instance a validation trace or a diagnostic payload consumers may branch on.

    instance: string

    The identity of this fault.

    A urn:uuid: URI unique across sessions and interfaces, so a reader keyed by it never passes over a new fault.

    Settings
    Member Visibility

    On This Page
    Properties