post
https://api.blockpeer.finance/api/blockpeer-trade/trade/registry/roles/remove
Remove an organization-level access role from an address for a specific Token Registry. Use this to revoke permissions such as the ability to issue (mint), accept, restore ETRs, or administer registry configuration.
How this fits in the Trade flow
- Called by the Integrating System
- Used when the End User organization needs to revoke access
- Updates registry RBAC configuration
- Requires explicit End User approval
- Approval happens only via redirect URL and End User passkeys
Role changes affect organizational control and therefore require End User approval.
What happens next
- The Integrating System redirects the End User to
redirectUrl - The End User reviews the role removal request
- The End User approves the action using passkeys
- The role is removed from the specified address
- The Integrating System updates its stored role configuration
Without End User approval, the role is not removed.
Responsibility clarification
- RBAC configuration belongs to the End User organization
- BlockPeer does not store organizational role mappings
- The Integrating System must store:
- Registry address
- Current role-to-address mappings
- Any internal permission model derived from these roles
BlockPeer acts purely as TradeTrust infrastructure.
Important notes
- Network transaction fees apply (paid by the End User-controlled account)
- Removing a role may block certain actions (e.g., issuance) immediately
- Consider using Get Role Status after approval to reconcile state
Common use cases
- Offboarding a user from the issuance team (remove MINTER)
- Revoking operational acceptance permissions (remove ACCEPTER)
- Restricting exception handling permissions (remove RESTORER)
- Tightening admin access (remove ADMIN)