Change which version of a document the organization is adopting
const url = 'https://api.adversarial.com/api/v1/documents/cisp';const options = { method: 'PATCH', headers: {'Content-Type': 'application/json'}, body: '{"adopting_version":"2026.9.1"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PATCH \ --url https://api.adversarial.com/api/v1/documents/cisp \ --header 'Content-Type: application/json' \ --data '{ "adopting_version": "2026.9.1" }'Setting adopting_version starts holding that version so it can be
configured from the new template’s defaults ahead of going live — no edits
carry over from the version it replaces, and the current version remains
the policy of record until the held version’s proposal is approved. Setting
it to null releases whatever is held.
Starting adoption denies any open proposal on the outgoing live version.
Idempotent in both directions: adopting the version already in force or already held, and releasing when nothing is held, all change nothing.
Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The document slug
Example
cispRequest Bodyrequired
Section titled “Request Bodyrequired”Request to change which version an organization is adopting.
object
The version to adopt, or null to release the one being adopted. The
field is required — a PATCH that names nothing is a client error, not
a silent no-op.
Example
2026.9.1Responses
Section titled “Responses”How the organization now stands
How an organization stands on one document: the version in force, and the
version it is adopting, if any. The body of GET/PATCH /documents/{slug}.
object
The version currently in force — the organization’s policy of record.
For an uninitialized document this is the template it would initialize
to; None while an adoption started from that state is in flight,
because the draft is then the only version the organization holds.
object
When the organization retired this version. Only set on archived rows.
The compliance-program section containing a document.
The edition of a document as YYYY.M.N: the year and month it was issued, then a sequence number counting editions issued in that month. Components carry no leading zeros.
The document has not been initialized yet. It is possible for the document to have details, meaning that a proposal is “open” to initialize it.
object
The initial proposal is being opened
object
The initial proposal is being opened
object
The edition of a document as YYYY.M.N: the year and month it was issued, then a sequence number counting editions issued in that month. Components carry no leading zeros.
The document has been initialized and is ready for use
object
The document has been initialized and is ready for use
object
The edition of a document as YYYY.M.N: the year and month it was issued, then a sequence number counting editions issued in that month. Components carry no leading zeros.
The version this row describes.
Whether a document version is the organization’s current one, a retired one it previously used, or an in-flight adoption draft.
Example
{ "adopting_version": "2026.9.1", "current": { "category": "governance", "latest_version": "2026.9.1", "slug": "cisp", "state": { "value": "uninitialized" }, "version": "2026.9.1", "version_state": "current" }}No registered template with this slug and version
A different version of this document is already being adopted