Skip to content
invoise

Team and access

Invite someone to the whole merchant account or to a single shop. Use a login session with merchant-owner access; a shop API key cannot manage the team.

Invite a teammate

Section titled “Invite a teammate”
Terminal window
curl -X POST 'https://platform.invoise.me/api/v1/merchants/{merchant_id}/invites' \
  -H 'Authorization: Bearer <session-token>' \
  -H 'Idempotency-Key: <saved-unique-key>' \
  -H 'Content-Type: application/json' \
  -d '{"provider":"email","subject":"[email protected]","role":"developer","shop_id":"<shop-id>"}'

Use viewer for reading, developer for integration work, or owner for administration. Set shop_id to limit the invitation to one shop. Omitting it or setting it to null grants access across the merchant.

Check the role and scope before sending. The selected shop must be active and belong to that merchant; an invalid shop does not fall back to merchant-wide access.

The recipient signs in and accepts with POST /api/v1/invites/{id}/accept. Send an idempotency key on this request too.

By default a merchant can have up to 10 members and pending invitations together. Beyond that, both inviting and accepting return 400 team_limit_reached; Invoise staff can raise the limit. See Limits.

View or remove access

Section titled “View or remove access”
Request Purpose
GET /api/v1/merchants/{merchant_id}/team list grants and invitations.
DELETE /api/v1/merchants/{merchant_id}/invites/{id} revoke a pending invitation.
DELETE /api/v1/merchants/{merchant_id}/grants/{id} remove existing access.

Changes require the appropriate owner session and idempotency key. If MFA is enabled, a sensitive operation may ask for a fresh code.

Blocked accounts

Section titled “Blocked accounts”

If Invoise staff block a merchant, its unpaid invoices are cancelled with reason merchant_blocked, its deposit addresses are disabled and its API keys stop working. Members see the reason in the dashboard.

A blocked user’s requests, other than wallet and card requests, return 403 account_disabled with the reason in error.details.

Export payment history

Section titled “Export payment history”

Download GET /api/v1/shops/{shop_id}/export.csv with shop read access. Use it for accounting exports, not as a payment notification.