Teams & Roles
Invite teammates, assign scoped roles, and require multiple approvals on sensitive actions — all backed by a real maker-checker workflow, not just a permissions label.
Roles & scopes
/team/rolesGET /team/roles/scopes lists every permission scope available to attach to a custom role — payments, payouts, refunds, cards, and settings each have their own read/write scopes.
Invitations
/team/invitationscurl-X POST https://api.binkpay.net/team/invitations \
-H "Authorization: Bearer sk_test_..." \
-d '{ "email": "finance@yourcompany.com", "roleId": "role_finance_ops" }'The invitee receives a token-based link (GET /team/invitations/token/:token) to accept or reject — no password is exchanged over the API.
Approvals (maker-checker)
/team/approvals/requestsSensitive actions — like issuing a card above a threshold — can be routed through an approval policy requiring one or more teammates to vote before the action executes. See the Approvals admin guide for the full workflow.
Audit trail
/team/auditEvery role change, invitation, and approval decision is logged here. GET /team/audit/export produces a downloadable export for compliance review.
Owner role can't be locked out
Ownership transfer (POST /team/transfer-ownership) is a separate, explicit action — a role change can never accidentally strip the last owner's access.
Was this page helpful?
