Overview
How Aidelly works and which integration path to choose.
Aidelly is a social media scheduler built for programmatic use. You can reach every Aidelly feature from three distinct layers:
| Layer | Best for | Entry point |
|---|---|---|
| REST API | Custom apps, backend automation, agents | https://app.aidelly.ai/api/public/v1 |
| MCP Server | Claude, ChatGPT, Cursor, any MCP client | https://app.aidelly.ai/mcp |
| Integrations | No-code workflows in Zapier, Make, n8n | Platform-native connectors |
Core concepts
Workspaces and brands
Every API call is scoped to a workspace (organization) and optionally a brand (a publishing identity within that workspace). Most endpoints accept:
x-aidelly-workspace-idheaderx-aidelly-brand-idheader
You can find these IDs in Account Settings → API Keys.
Posts
A post is a single piece of content scheduled or published to one social platform account. Posts have a lifecycle:
draft → scheduled → publishing → completed
failed
canceledMedia
Upload images and videos first via the signed upload URL endpoint, then reference the returned read_url when creating posts.
Idempotency
All write endpoints (POST, PATCH) require an Idempotency-Key header. Use a stable key per logical write and reuse the same key on retries. See Idempotency for details.
Requirements
- An active Aidelly subscription (Launch, Scale, or Agency)
- At least one social account connected in the Aidelly dashboard
- An API key with the required scopes