Skip to main content

Permissions

When authenticating the user with OAuth2, you can specify what data the token will have access to by choosing one or more access scopes.

Scopes

Here is the list of all scopes you can request:

Scope SlugDescription
loginAuthenticate with the user
allFull access to all available resources
readCan read data, cannot execute operations
writeCan execute operations related to released resources
emailView email address
phoneView the phone number used in registration
profileView basic profile data (name and photo)
profile.legalView legal data (legal name and CPF)
profile.genderView gender
profile.preferencesView preferences (languages and time zone)
acbr.accountsManage accounting accounts and tax integrations
admin.subaccountsManage sub-accounts of the main account
admin.usersManage users and permissions
automation.email_accountsManage email accounts for automation
automation.email_deliveriesView and manage email deliveries
automation.sms_accountsManage SMS accounts
automation.sms_deliveriesView and manage SMS deliveries
automation.webhook_deliveriesView and manage webhook deliveries
automation.webhooksManage webhooks and automated notifications
billing.transactionsView billing and invoicing transactions
charge.automatic_pix.accountsManage automatic Pix accounts
charge.automatic_pix.locationsManage automatic Pix locations
charge.automatic_pix.pixManage automatic Pix charges
charge.automatic_pix.recurrencesManage automatic Pix recurrences
charge.automatic_pix.requestsManage automatic Pix requests
charge.bank_billet_accountsManage bank billet accounts
charge.bank_billet_paymentsView and register bank billet payments
charge.bank_billet_registrationsManage bank billet registrations in banks
charge.bank_billetsManage bank billets
charge.customer_subscriptionsManage customer subscriptions
charge.installmentsManage installments
charge.paymentsView and manage received payments
charge.pixManage Pix charges
charge.pix_accountsManage Pix accounts
data.bank_billet_queriesQuery bank billet information
core.providersManage system providers (banks and integrations)
crm.customersManage customers and commercial information
crm.peopleManage people and contacts
financial.accountsManage financial accounts
financial.balancesView balances and financial movements
financial.providersManage financial providers and bank integrations
financial.statement_transactionsView transactions and financial statements
integration.certificatesManage digital certificates for integrations
integration.commandsQuery account commands
integration.connectionsManage connections with banks and providers
integration.dischargesManage bank return files (discharges)
integration.edi_boxesManage EDI mailboxes for file exchange
integration.remittancesManage bank remittance files
mailbox.entriesManage mailboxes for receiving files
mailbox.filesView and manage files in mailboxes
partner.bank_contractsManage bank contracts with partners
payment.accountsManage payment accounts
payment.bank_billetsMake bank billet payments
payment.batchesManage payment batches
payment.darfsMake DARF payments (federal taxes)
payment.paymentsManage all types of payments through the API
payment.pixMake payments via Pix
payment.taxesMake tax and fee payments
payment.dda_accountsManage DDA accounts (Direct Debit Authorization)
payment.dda.bank_billetsView and manage DDA billets available for payment
payment.utilitiesMake utility bill payments (water, electricity, etc)
security.access_tokensManage access tokens and authentication
system.eventsView system events and logs
system.importsManage data imports
system.reportsGenerate and view system reports
transfer.accountsManage transfer accounts
transfer.batchesManage transfer batches
transfer.internalPerform internal transfers between accounts
transfer.pixPerform transfers via Pix
transfer.tedPerform TED transfers (Transferência Eletrônica Disponível)
transfer.transfersManage all types of transfers (Pix, TED, Internal) via unified endpoint

OAuth2

For OAuth2, permissions are accessed through the scope parameter in your OAuth2 request.

For example, your application may need to log in as the user to generate bank billets, but will not need to know the user's bank data.

The default permission is login if you do not specify a scope.

Permission groups

You can request permissions individually or in groups.

Group permissions should be separated with a + character in the URL.

Below is an example of a request URL with the scope parameter at the end:

[https://api-sandbox.kobana.com.br/v1/oauth/authorize?response_type=code&client_id=YOUR_CLIENT_ID&redirect_uri=YOUR_CALLBACK_URL&scope=login+email+profile](https://api-sandbox.kobana.com.br/v1/oauth/authorize?response_type=code&client_id=YOUR_CLIENT_ID&redirect_uri=YOUR_CALLBACK_URL&scope=login+email+profile)