Product configurations
Try a new version
Exactly the body a new version takes, run through exactly its checks — the configuration, the frame, the currency it was born in — and nothing written.
POST
The version write’s twin. It takes the new-version body byte for byte, checks what the write checks in the order the write checks it — the configuration exists for this Tenancy, the frame of its Archetype, the currency the configuration was created in — and stores nothing. A body the write would store answers
200 with the Archetype and the values as the write would read them back; a body it would refuse meets the write’s own refusal.
No idempotency key is read.
Path parameters
string
required
The Tenancy writing.
string
required
The configuration the version would belong to. Another Tenancy’s and one that never existed are both
404, exactly as on the write.Body
The new-version body:values, and nothing else.
Response
archetype, values, effective and advisories — as the creation preview answers, the same advisories the new version would answer for the same body. No version: the number is the write’s to take.