Published Retrievers

Reconcile Publish State

Changed on

Repair published_retrievers <-> marketplace_listings divergence.

A retriever's public surfaces can drift apart — e.g. a marketplace listing exists but its published_retrievers record is missing, so /v1/public/retrievers/{name} 404s (half-published). This detects the state and (unless dry_run) repairs it idempotently:

  • missing_published -> create the published record from the listing (reused id)
  • missing_listing -> create the listing from the published record
  • consistent -> ensure cross-link
  • not_published -> no-op
post/v1/retrievers/{retriever_id}/publish/reconcile

Request

  • Base URL: https://api.mixpeek.com
  • URL: https://api.mixpeek.com/v1/retrievers/{retriever_id}/publish/reconcile
  • Auth: HTTP bearer and API key in header X-Namespace

Path parameters

retriever_idstring required

ID of the retriever to reconcile

Query parameters

dry_runboolean

Report the divergence state without mutating

Response

Successful Response

object required

Changes

  • 61a175e8eb9aRevision 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

  • 5d4c905106b4Revision changes
    • info

      the endpoint scheme security BearerAuth AND NamespaceHeader was added to the API