MenuPublication

Schema

One publication and its per-store, per-platform outcomes.

A publication submits each targeted storefront's COMPLETE active menu set, because delivery platforms replace rather than merge. Publishing menu A to a storefront that also carries menu B therefore submits both, and menuId is then omitted: it is present only when every store on the publication received exactly one and the same menu.

Fields

publicationIdstring
The publication's identifier — the publicationId publishMenu returned.
menuIdstring
The single menu this publication submitted, when every store on it agrees on exactly one. Absent otherwise — see the MenuPublication description.
statusstring
The publication's overall state:
- queued — accepted, no store work started.
- publishing — at least one store has not finished: its menu is being sent, or the platform has not answered yet. A publication with a DoorDash store stays here until DoorDash confirms or rejects the menu, usually within a few minutes.
- completed — finished. This INCLUDES a publication where some stores failed; check each stores[].status.
- failed — the publication as a whole failed or was cancelled.
Possible values: [queued, failed, publishing, completed]
requestedAtstring
When the publication was requested — UTC, ISO-8601.
completedAtstring
When the publication reached its final state (completed or failed) — UTC, ISO-8601. Absent while status is queued or publishing. On a publication recorded before its finishing time was tracked exactly, this is the time the publication was last updated: a close approximation of when it finished, not an exact value.
storesMenuPublicationStore[]
Every store this publication targeted, with its per-store, per-platform outcome.