DailyAPI Documentationv1

Permissions

Assign least-privilege access using the exact permissions available in Daily.

View OpenAPI

Select at least one available permission when creating a key. The API checks the exact permission required by each documented operation after authentication, subscription, and IP restrictions. A missing permission returns 403 insufficient_permission.

Product label (exact)PermissionProtected endpointsPurpose
פרטי העסקbusiness:readGET /businessBusiness identity, contact details, and basic configuration.
לקוחותcustomers:readGET /customers, GET /customers/{id}Customer records and their saved contact data.
ספקיםsuppliers:readGET /suppliers, GET /suppliers/{id}Supplier records and their saved contact data.
לידיםleads:readGET /leads, GET /leads/{id}Leads, contact data, status, and assigned owner summary.
מוצרים ושירותיםproducts:readGET /products, GET /products/{id}Products, raw materials, prices, and catalog metadata.
מסמכיםdocuments:readGET /documents, GET /documents/{id}, GET /documents/{id}/pdfDocuments, line items, relationships, and available PDFs.
תשלומיםpayments:readGET /payments, GET /payments/{id}Recorded payments and document relationships, without sensitive payment details.
מלאיinventory:readGET /inventory, GET /inventory/movementsInventory levels and inventory movements.
משימותtasks:readGET /tasks, GET /tasks/{id}Tasks, dates, statuses, and linked business objects.

Existing read permissions are preserved. New write permissions require explicit consent; existing keys do not gain them automatically.

Least privilege

Create a separate key per integration and enable only the rows it needs. This limits exposure, makes usage visible by key, and lets you rotate or revoke one integration without interrupting another.

Permissions can be edited later in Daily. Removing a permission takes effect on subsequent requests; no new key is required.

Missing-permission response

{
  "error": {
    "type": "authorization_error",
    "code": "insufficient_permission",
    "message": "This API key cannot access customers."
  },
  "request_id": "req_docspermissions01"
}

Treat this response as configuration failure. Do not retry it automatically; ask the primary business owner to review the key's permissions.

Additional permissions

PermissionOperation
customers:writeManage the customer lifecycle
suppliers:writeManage the supplier lifecycle
leads:writeManage the lead lifecycle
products:writeManage product and raw material lifecycles
documents:writeManage document and draft lifecycles
tasks:writeManage the task lifecycle
inventory:writeManage inventory
expenses:writeManage expense, category, and payment lifecycles
tags:writeManage the tag lifecycle
expenses:readRead expenses, categories, and payments
tags:readRead tags

business:read also covers agent lists and bank account IDs. products:read covers raw materials. documents:read covers drafts. See permissions for combined operations.

On this page