Approve or deny a version's open proposal
const url = 'https://api.adversarial.com/api/v1/documents/ramp/versions/2026.9.1/proposal';const options = { method: 'PATCH', headers: {'Content-Type': 'application/json'}, body: '"approve"'};
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/ramp/versions/2026.9.1/proposal \ --header 'Content-Type: application/json' \ --data '"approve"'Approving a version the organization holds but has not promoted is the adoption commit point: it becomes the policy of record and the version it replaces is retired, atomically with the approval. Denying such a version abandons the adoption instead — the same outcome as releasing it — because a held version with a decided proposal has no way back into the workflow.
Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The document slug
Example
rampThe document version
Example
2026.9.1Request Bodyrequired
Section titled “Request Bodyrequired”Defines in a modification or creation standpoint, what happens to a proposal
todo: fix this doc
Responses
Section titled “Responses”Proposal decided on
object
A decision to approve a proposal and effect the consequences
The slug and version pair that uniquely identifies a document.
As a string it is written slug:version — for example cisp:2026.9.1.
object
The slug of the document. i.e. cisp
The version of the document. i.e. 2026.9.1
Example
{ "document": { "version": "2026.9.1" }}The latest proposal has already been decided, or the version is archived
No such version, or it has no proposal