Stops one spec generation from being the active desired state.
const url = 'https://example.com/v1/m/sessions/protocol-binding-specs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/disable?mode=validate';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"plan_hash":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url 'https://example.com/v1/m/sessions/protocol-binding-specs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/disable?mode=validate' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "plan_hash": "example" }'Stops one spec generation from being the active desired state.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Path parameter id.
Header Parameters
Section titled “Header Parameters ”Target tenant id; required when the principal can act in more than one tenant.
Canonical UUID required when mode=apply; reuse it only for an exact retry.
SHA-256 plan hash required when mode=apply; apply must reproduce it. For state transitions it must agree with body.plan_hash when both are supplied.
Strong ProtocolBindingSpec ETag required when mode=apply; when supplied in validate or plan it must match the current version.
Query Parameters
Section titled “Query Parameters ”Mandatory authoring phase. The server derives a fresh capability witness; validate and plan are observational, while apply revalidates and commits the spec transition.
Request Body
Section titled “Request Body ”Optional spec-transition plan precondition. The body may be empty in validate and plan; apply still requires a matching plan hash through this field or If-Plan-Hash.
object
Optional plan precondition; it must agree with If-Plan-Hash when both are supplied.
Example generated
{ "plan_hash": "example"}Responses
Section titled “ Responses ”OK
object
Example generated
{}Bad request
object
Example generated
{}Unauthenticated
object
Example generated
{}Forbidden
object
Example generated
{}Not found
object
Example generated
{}Conflict / setup required
object
Example generated
{}ETag or plan precondition failed
object
Example generated
{}Apply precondition required
object
Example generated
{}Rate limited
object
Example generated
{}Required store is unavailable
object
Example generated
{}