Propose relocating an authored SRG requirement
POST
/rules/{ruleId}/relocations
Creates an OPEN relocation proposal for an authored requirement of an SRG component, naming the destination SRG's abbreviation. Requires author role on the component. One open proposal per requirement; a second returns 422. The proposal is a record, never a status change on the requirement — the destination SRG's authors concur or non-concur.
Authorizations
tokenAuth
Personal access token authentication. Send via Authorization header: Authorization: Token vulcan_xxx. Tokens are SHA-256 hashed server-side (never stored in plaintext). Scopes: read (GET), write (mutations), admin (everything). Create tokens via Settings → API Tokens in the web UI.
Type
HTTP (token)
Request Body
application/json
JSON "requirement_relocation": { "target_technology_token": "CTR" }
{
}
Responses
Relocation proposed
application/json
JSON "toast": { "title": "Relocation proposed.", "message": [ "Proposed for the CTR SRG." ], "variant": "success" }
{
}