Groups
The Partner API exposes group endpoints so you can query proposals and obtain transaction signing payloads for the authenticated partner's group policy (e.g. multi-signer groups). The intent is for partners to get signing payloads via API and send them to third parties — including qualified custodians (e.g. BitGo) — to sign, instead of going through the UI. Full request/response details are in the Partner API OpenAPI spec — Groups.
These endpoints are under construction and are not yet in active use. Behavior and availability may change.
Request sequence
| Step | Action | Request |
|---|---|---|
| 1 | Get proposals for the partner's group | GET /api/v1/groups/proposals |
| 2 | Get vote transaction payload | GET /api/v1/groups/submit-vote |
1. Get proposals
Get proposals: GET /api/v1/groups/proposals
Optional query: offset, limit, status. Returns proposals (e.g. send crypto, withdraw, add multi-signer, add user) with status, tally, voting period, and metadata.
2. Get vote transaction payload
Get vote transaction payload: GET /api/v1/groups/submit-vote
Query: proposal_id, option (YES, NO, ABSTAIN, VETO), voter_address. Optional: exec, justification. Returns a transaction payload for signing and broadcasting; the vote is executed when that transaction is submitted to the chain or via the appropriate flow.
For full request/response schemas and parameters, see the Groups spec.