Product configurations
Write a new version
Change the terms by writing the next version whole. Every earlier version stays readable, and no issued loan moves.
POST
A configuration is never edited: a change is the next version, stated whole. The body is the values alone — the Archetype and the identifier were fixed at creation, and the path names the configuration — and the same frame checks apply, as at creation. Try the body first: the preview takes it, runs these checks, and writes nothing.
Path parameters
string
required
The Tenancy writing.
string
required
The configuration the version belongs to.
Headers
string
Your own value, up to 255 bytes. This route carries no reference of yours, so the key is what makes a retry safe: the first outcome — refusals included — is recorded and answers every identical repeat for 24 hours, marked
Idempotent-Replayed: true. The same key with a different request is 422 idempotency_mismatch.It is the fifth line of the signed canonical string, so sign with the key you send. Retries carries the whole rule.Body
object
required
The terms, whole — every field the frame requires, restated. A version is not a diff: what it does not state, it does not have.
Response
201 with the stored configuration at its new version, counting from 1 and rising by one, with effective beside values and the advisories the body earns — as creation answers them. An advisory refuses nothing.
Refusals
Everything creation refuses, plus a body namingarchetype — the shape never changes.