Skip to main content

Overview

Publishes processed photos to the public event gallery by triggering metadata mapping. This is pipeline step 3, after Process. For API-key requests, the job is asynchronous: this endpoint only queues work. The response returns status: "processing"; track completion with Pipeline Status via stages.go_live.status (processed or failed) and is_live (true when live). Once complete, photos appear on the public gallery and through search endpoints (All Photos, BIB Search, Face Search).
Photos must be processed before going live. If no processed images exist, this endpoint returns a 400 error.

Endpoint

Path Parameters

Example Request

Example Response

Error Responses

See Errors for canonical descriptions and retry guidance.

OAuth Request

OAuth only. Read calls require events:read. Writes require both events:read and events:write, plus an accepted organiser admin membership. Send a bearer token without X-API-Key. The API-key request and response above remain unchanged. For OAuth, use the same path with the JSON body below. Publishing uses no credits and runs in one call: send mode: "execute" with a stable idempotency_key. No review token or confirmation is needed; mode: "preview" is an optional dry run. See Operations for retry rules.
Publishing makes the event live: participants can open the gallery once publishing completes. Tell the user before calling it. Unpublish moves the event back to draft.

Example Request

Example Response

OAuth Response Models

GuardedOperationData replaces the API-key stage-start response. Track operation_id through Operations, alongside Pipeline Status. pending or queued means the work was accepted, not completed; uncertain dispatch is dispatch_unknown.