Skip to main content
A version’s APIs cannot be called until it is published. Publish sits in the destination header.
1

Click Publish

The publish confirmation
2

Confirm

Click Yes, publish. The button becomes Publishing and the status card follows the run.
Once a version is published you can no longer add endpoints to it, only edit the ones it has. Get the endpoint set right before publishing — afterwards, adding one means a new version.

​
When Publish is blocked

The button is disabled, with a tooltip, when: If you have unsaved endpoint changes, Studio asks before publishing and discards them if you continue — save first.

​
Follow the run

While publishing, hovering the Publishing button shows the steps of the run, each with its status and timestamp, and the error message for any step that failed.

​
Retry and restart

A version stops when a card schema it depends on breaks. Restarting works once the card is valid again; if it is not, fix the card query and create a new version.

​
Update a published version

Some changes can be published onto a live version without creating a new one — adding properties, segments and relations, and enabling facets. None of them change the shape of what consumers already read. Saving one of those puts the version into Pending changes and brings Publish back. See Pending changes.
Publishing pending changes onto a live version shows an Updates impact warning per risky change. Read them before confirming — this API is already being called.
Anything that would break the existing contract — removing a property, renaming an alias, adding an endpoint or a language — needs a new version.