Collection Documents

Per-document support diagnostics (visibility, failures, history).

Changed on

Answer three support facets for ONE document that no other surface exposes: (1) visibility_reason - are this document's vectors present in MVS (searchable) and, if not, why (the Unsearchable class, made per-document answerable via the vector-presence machinery); (2) recent_failures - the source object's own status/error, with an honest note that structured batch errors are aggregate-only; (3) diagnostic_history - the document's processing history from its own _internal records. Every facet returns a real value, or an empty/None value with a reason naming what would carry it.

get/v1/collections/{collection_identifier}/documents/{document_id}/diagnostics

Request

  • Base URL
    https://api.mixpeek.com
  • URL
    https://api.mixpeek.com/v1/collections/{collection_identifier}/documents/{document_id}/diagnostics
  • Auth
    HTTP bearer and API key in header X-Namespace

Path parameters

collection_identifierstring required

The ID or name of the collection.

document_idstring required

The ID of the document.

Response

Successful Response

document_idstring required
collection_idstring required
source_object_idstring nullable

The document's originating bucket object id (lineage root).

Changes

    • warning

      removed the optional property from the response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the optional property to the response with the status

    • info

      added the required property to the response with the status

    • info

      added the required property to the response with the status

    • info

      endpoint added