Publishing
An itinerary is a draft that only your organization's members see. Publishing copies the draft into a publication, which is what embeds, share links, route files and tiles show. Publishing needs Map Publishing in your agreement.
Writes act as a member, so mint a session token that names one, as in the quickstart:
The examples below publish $ITINERARY_ID, an itinerary of yours with at least one segment.
POST on the itinerary's publication publishes its current draft. It takes no body and is safe to repeat.
Edits change the draft only. The itinerary reports has_unpublished_changes until you publish again.
Visitors still see the published version. Publish again to show the edit.
DELETE on the publication stops serving the itinerary. The draft stays, and you can publish it again later.
A collaborator's edit names them in the answer:
A zone publishes the same way, at /v1/zones/{zone_id}/publication. Collection embeds and collection share links show a zone once it is published and public.