Home / API Reference / API Permissions Reference

API Permissions Reference

Permission strings for each endpoint

What it is

API keys require specific permissions to access each endpoint. This reference lists the permission string for every API route.

Permission format

{resource}.{action} where resource = first path segment (e.g. clients), action = read, create, update, or delete.

Full permission table

EndpointMethodPermission
/clientsGETclients.read
/clientsPOSTclients.create
/clients/{id}GETclients.read
/clients/{id}PUTclients.update
/clients/{id}DELETEclients.delete
/productsGET, POSTproducts.read, products.create
/products/pricingGETproducts.read
/products/{id}GET, PUT, DELETEproducts.read, products.update, products.delete
/servicesGET, POSTservices.read, services.create
/services/{id}GET, PUT, DELETEservices.read, services.update, services.delete
/services/{id}/provision, suspend, unsuspend, terminatePOSTservices.update
/invoicesGET, POSTinvoices.read, invoices.create
/invoices/{id}GET, PUTinvoices.read, invoices.update
/invoices/{id}/payPOSTinvoices.update
/paymentsGET, POSTpayments.read, payments.create
/serversGET, POST, PUT, DELETEservers.read, servers.create, etc.
/api-keysGET, POST, PUT, DELETE, revoke, rotateapi-keys.*
/webhooksGET, POST, PUT, DELETEwebhooks.*
/audit-logGETaudit-log.read

Wildcards

Use client.* for all client operations, or * for full access.

Was this helpful?

Tags: API