Daily Public API
Build secure, business-scoped integrations with Daily data and supported workflows.
The Daily Public API provides business-scoped access to data and supported workflows in Daily. Daily supports read and write integrations for operations enabled for the integration. This reference lists the exact methods, paths, permissions, and schemas currently published in the maintained v1 contract; never infer a write route from a resource name alone.
API at a glance
| Property | Value |
|---|---|
| Production base URL | https://api.godaily.co.il/v1 |
| Current version | v1 |
| Authentication | Bearer API key |
| Documented operations | See the resource reference |
| Data scope | The active business bound to the key |
| Default / maximum page size | 50 / 100 |
| Response format | JSON |
The contract includes read and write operations. The write guide explains permissions, fields, idempotency, and entity deletion rules.
What you can retrieve
- Business identity and contact details
- Customers and suppliers
- Leads
- Products and raw materials
- Documents, line items, and short-lived PDF download links
- Recorded payments without sensitive payment details
- Inventory levels and movements
- Tasks and their business relationships
Five-minute quickstart
- Open API keys in the Daily application.
- Create a key with the פרטי העסק (
business:read) permission. - Save the one-time key in your server's secret manager or as
DAILY_API_KEYin a secure local shell. - Send
GET https://api.godaily.co.il/v1/businesswithAuthorization: Bearer $DAILY_API_KEY. - Record the response's
request_id; Daily support can use it to trace a request safely.
Continue with the complete getting-started guide.
Integration boundaries
The API is designed for server-to-server integrations. Never ship a Daily API key in a browser bundle, desktop client, or mobile application. The documentation playground is an explicit testing exception: its key exists only in the current page's React memory and requests go directly to Daily.
Daily API keys are secrets. Do not put them in source control, URLs, logs, issue trackers, or chat messages.