DOCUMENTATIONv2

GET

Governance

List proposals

/api/v2/governance/proposals

AUTHENTICATIONBearer token · governance:readAUTHORITATIVE OWNERgovernance-serviceCONTRACT AUTHORITYGenerated Rust OpenAPISTATUSSource ready · production listed

PURPOSE + BUSINESS CONTEXT

List governance proposals visible to the caller.

WHEN THIS CALL IS USEFUL

Call this when a workspace governor, policy administrator, custody participant, or governance agent needs to discover proposals and choose a canonical record for a later step so it can make a proposal, authority, decision, or ceremony transition under the correct quorum and policy.

OUTCOME · Discover

What changes

Read-only projection; it grants no mutation, settlement, traffic, or authority change.

WHY IT MATTERS

Gives people and agents a contract-backed way to discover proposals.
Keeps deliberation, approval evidence, authority assignment, and threshold-signing participation explicit and auditable.

ISOLATION + AUTHORITY

Tenant, workspace, proposal, voter, authority assignment, quorum, custody participant, and signing-session boundaries remain separate. A proposal, recorded decision, assigned role, or ceremony request does not by itself activate a contract, produce a threshold signature, move value, or grant publisher, matching, or trading authority.

BEFORE YOU CALL

Authenticate at the documented boundary: bearer+scope.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Resolve the current proposal or assignment version, eligible authority, quorum rule, and purpose-bound policy before relying on this result.

WHAT TO DO NEXT

Select one canonical identifier from the response and open its detail operation when the live contract exposes one.
Re-read the proposal, assignment, quorum, or ceremony state and verify its version and commitments before advancing the governed action.

AGENT GUIDANCE

Use proposals only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Keep proposal creation, review, decision recording, quorum satisfaction, authority assignment, ceremony request, participant signing, execution, and finality as separate lifecycle facts.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

MACHINE CONTRACT

The exact deployed parameters, schemas, responses, security requirements, and Hybrid-Chain agent metadata are authoritative at this operation's production OpenAPI JSON Pointer. The readable tables below add integration guidance; the deployed OpenAPI controls if guidance and the machine contract ever differ.

Open the authoritative production contract ↗

EXTENDED INTEGRATION GUIDANCE

Readable request and response reference

Examples illustrate integration intent; the referenced OpenAPI operation and component schemas define the executable shape.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE

AuthorizationheaderRequired

Bearer tokenCredential containing governance:read authority.EXAMPLEBearer hc_live_…

X-Request-IDheaderOptional

stringOptional caller correlation identifier. The gateway emits the effective value on the response.

RESPONSES

Status and payload examples

200Canonical resource projection.Read completed · JSON RESPONSE+

{
  "proposals": [
    "example-proposal"
  ]
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then select one canonical identifier from the response and open its detail operation when the live contract exposes one.
RETRY SAFETY: Repeat only when the integration needs a fresher authoritative projection.
STATE RECONCILIATION: Use returned identifiers and versions as the comparison point for later reads. Refresh the proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.

401Bearer credential is missing, expired, or invalid.Authentication required · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Discard the rejected credential, complete the documented authentication or reassertion flow, and rebuild any request signature with fresh timestamps and nonces.
RETRY SAFETY: Retry only with a newly valid credential and fresh replay-protection values. Do not replay an expired signature.
STATE RECONCILIATION: Authentication failed before an authoritative read was returned for workspace governance proposals, approvals, signing handoffs, policy versions, and execution evidence.
ESCALATE WHEN: Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.

403The principal lacks the required scope, role, tenant, or step-up authority.Authority or policy denied · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Verify the exact scope, tenant or workspace membership, owner boundary, step-up purpose, feature policy, and resource eligibility. Never broaden authority automatically.
RETRY SAFETY: Do not retry until the missing authority or policy condition has been deliberately resolved with least privilege.
STATE RECONCILIATION: Confirm the caller and resource resolve to the same authority boundary for workspace governance proposals, approvals, signing handoffs, policy versions, and execution evidence.
ESCALATE WHEN: Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.

503The authoritative service or read model is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Treat the failure as transient and preserve the last known good representation without presenting it as fresh.
RETRY SAFETY: Retry with bounded exponential backoff and jitter; stop after the integration's failure budget is exhausted.
STATE RECONCILIATION: Refresh the proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN: Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.

OPERATIONAL NOTES

Security and lifecycle guarantees

List governance proposals visible to the caller. Authoritative owner: governance-service.
The Rust gateway validates the public contract and routes only to the authoritative owner; clients never address internal services directly.
The tables and examples are derived from the current gateway source OpenAPI. Re-fetch the deployed OpenAPI before execution; deployment status is shown separately on this page.
Only parameters present in the OpenAPI operation are accepted; undocumented query keys fail closed with HTTP 422.

DOCUMENTATION STATUS

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-09-11T06:35:11.572Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation ↗Return to the V2 directory ↗