post
https://api.blockpeer.finance/api/blockpeer-trade/trade/registry/getRole
Retrieve the current role assignments for a specific Token Registry. This endpoint allows an Integrating System to determine which addresses are authorised to perform actions such as issuing, accepting, or restoring electronic trade documents (eBL / ETRs).
How this fits in the Trade flow
- Called by the Integrating System
- Used after roles are assigned or updated
- Returns the current RBAC configuration
- Does not require End User approval
- Safe to call at any time
This is a read-only endpoint.
Responsibility clarification
- Role assignments belong to the End User organization
- BlockPeer does not maintain organisational state
- The Integrating System should:
- Store role mappings internally
- Enforce business logic and UI permissions
- Use this endpoint for reconciliation or audits
Important notes
- This endpoint:
- Does not modify any state
- Does not require redirect approval
- Does not incur network transaction fees
- Results reflect the current on-chain registry state
Common use cases
- Display authorised signers in an admin UI
- Validate whether an address can issue an eBL
- Perform permission checks before initiating actions
- Reconcile internal records with registry state