Developer docs
Dayline API reference.
Authentication, endpoints, webhooks and the MCP server, with examples.
Authentication
Create a key under API keys in your workspace. Send it as a bearer token: Authorization: Bearer YOUR_KEY. Keys belong to one workspace and can be revoked at any time.
Base address
REST: /api/v1. MCP: /api/mcp. Both addresses are shown on the API keys page with your host.
Posts
GET /api/v1/posts lists posts with status, schedule and channels. POST /api/v1/posts creates a draft or scheduled post with content per channel. GET, PUT and DELETE /api/v1/posts/{id} read, change and remove one.
Media
GET /api/v1/media lists library items. POST /api/v1/media uploads a file (multipart) or imports from a URL.
Accounts
GET /api/v1/accounts lists connected channels with their provider, name and status.
Contacts
GET /api/v1/contacts lists people your automations and inbox have talked with, with tags and details they gave.
Webhooks
GET and POST /api/v1/webhooks manage subscriptions. Events: post.published, post.failed, inbox.item_received, contact.created, contact.message_received and contact.handed_off. Payloads are signed with your webhook secret; verify the signature header before trusting a delivery. Failed deliveries are retried with backoff.
Rate limits
60, 120 or 600 requests a minute depending on the plan. Responses include the usual remaining and reset headers.
Errors
JSON with a message and, for validation, an errors object keyed by field. 401 for a bad key, 403 for a missing permission or plan feature, 422 for validation, 429 when rate limited.