Manage Checkout Lifecycle
Renames, publishes, unpublishes, archives, restores, or promotes the checkout. The body carries any combination of name, description, status, and is_default — at least one field is required (an empty body is rejected with 400). Status transitions follow the lifecycle state machine: publish (PUBLISHED) is only valid from NOT_PUBLISHED; an ARCHIVED checkout is restored in two steps (status: NOT_PUBLISHED first, then status: PUBLISHED); patching to the current status is rejected. Metadata (name/description) remains editable while ARCHIVED. is_default accepts only true: it promotes the checkout to account default, force-publishing it from any state, and atomically demotes the previous default; when is_default: true is sent together with status, the promotion wins and status is ignored. The default checkout cannot be archived or unpublished.
Request
- Base URLhttps://api-sandbox.y.uno/v1
- AuthAPI key in header PUBLIC-API-KEY and API key in header PRIVATE-SECRET-KEY
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
The unique identifier of the checkout to update (UUID, 36 chars). Non-UUID values are rejected with 400 before processing.
Headers
Optional client key, up to 64 characters. Best-effort — re-sending the same key is not guaranteed to be de-duplicated.
Request body
Response
The updated checkout summary. The identifier is exposed as the top-level id. Read the resulting status with the Fetch endpoint.
Changes
No recorded changes to this operation across all 1 revision of this API.