Resume Exchange (SUSPENDED -> ACTIVE) — shares scope with activate per OQ-19

Returns a SUSPENDED Cryptographic Exchange to ACTIVE and republishes the linked
Capability Grant projection.

The body carries the optimistic-lock version and NOTHING ELSE.
Resume records no justification: restoring a capability generates no grievance
for the audit trail to answer, which is the PRD 224 exclusion this operation
inherits. A body that still carries reason is REFUSED with 400
rather than silently ignored - the request type has no such component and strict
deserialization is enabled - so a caller migrating off the retired shared
transition body learns that the value was never being recorded.

Authorization: requires scope admin.tenant.exchange.activate,

the same scope that governs activation (OQ-19). There is no .resume scope.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required
Body Params

Resume a SUSPENDED Cryptographic Exchange. Carries the optimistic-lock version only — resume records no justification, and a body carrying reason is refused.

int32
required

JPA @Version optimistic-lock discriminator, as last read from the exchange detail response. A stale value is refused with 409.

Response

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
*/*