Authentication

Permissions

See which permissions an API key can use and what each permission unlocks.

Modified at Apr 28, 2026, 05:38 AM UTC

Permissions define the authenticated API features a key can access. The dashboard and GET /api/me expose these permissions so users do not have to infer access from errors.

When creating an API key, the dashboard groups grantable permissions by product area and lets you review the selected codes before the key is created. After creation, the key detail page shows the saved permission set so the user can audit what the key can do.

Common Client Permissions

AreaPermission codeDescription
Publicpublic.service.readRead public services listing.
Useruser.me.readRead current authenticated principal.
Walletwallet.balance.readRead wallet balance.
Walletwallet.ledger.readRead wallet ledger mutations.
Depositdeposit.provider.listList available deposit providers.
Depositdeposit.createCreate deposit.
Depositdeposit.readRead deposits.
Serviceservice.listList services.
Serviceservice.read_detailRead service detail.
Orderorder.createCreate order.
Orderorder.readRead one order.
Orderorder.listList own orders.
Transactiontransaction.readRead transactions.
Transfertransfer.createCreate transfer.
Transfertransfer.readRead transfers.
Uploadupload.presigned.createCreate presigned upload URL.
Uploadupload.completeComplete upload.
Ticketticket.createCreate ticket.
Ticketticket.read.selfRead own tickets.
Ticketticket.reply.selfReply to own ticket.
Ticketticket.tag.selfManage tags on own ticket.

If a request returns 403, the API key is valid but its effective permissions do not include the permission required by that endpoint.