reeldeploy.THE DEVELOPER CORNER

Your content. Your workflow.

Publish once. Deploy everywhere. Use the REST API or the Reeldeploy MCP server to connect your apps and agents.

Authentication

Create an API key in Settings. Use a live key to publish. Test keys are read-only. All requests are scoped to the key’s workspace.

Authorization: Bearer rd_live_YOUR_KEY
Content-Type: application/json

API base: https://api.reeldeploy.com/v1

The publishing flow

Connect and sync social accounts in the dashboard, then GET /accounts.
POST /media/upload-url with mime and sizeBytes. PUT your file to the returned uploadUrl.
POST /media/:id/complete to inspect the upload.
POST /posts with account targets, a caption, and your media IDs.
GET /posts/:id to inspect each target’s outcome.

{
  "type": "video",
  "caption": "Something worth sharing.",
  "mediaIds": [
    "YOUR_MEDIA_UUID"
  ],
  "targets": [
    {
      "accountId": "YOUR_ACCOUNT_UUID",
      "overrides": {
        "title": "A new perspective",
        "madeForKids": false,
        "privacy": "public"
      }
    }
  ],
  "scheduledAt": "2027-01-10T14:00:00+01:00"
}

Endpoints

Method	Endpoint	Purpose
`GET`	`/health`	`Service health`
`GET`	`/accounts`	`Connected accounts`
`POST`	`/media/upload-url`	`Reserve an upload`
`POST`	`/media/:id/complete`	`Validate media`
`POST`	`/posts`	`Publish or schedule`
`GET`	`/posts`	`Filter by status, from/to creation date, limit, offset`
`GET`	`/posts/:id`	`Post and target status`
`PATCH`	`/posts/:id`	`Reschedule a pending post`
`POST`	`/posts/:id/cancel`	`Cancel entirely pending posts`
`POST`	`/posts/:id/retry-failed`	`Retry safely retryable targets`

MCP

The server exposes list_accounts, upload_media, schedule_post, publish_now, list_posts, get_post_status, and cancel_post. Set REELDEPLOY_API_KEY and run the local server over stdio. Hosted HTTP mode requires an additional transport token.

REELDEPLOY_API_KEY=rd_live_YOUR_KEY
REELDEPLOY_API_URL=https://api.reeldeploy.com/v1

pnpm --filter @reeldeploy/mcp exec tsx src/index.ts

Errors and delivery

Errors use an error object containing code, message, and optional details. Time values must include a timezone offset. A processing response is not a publication confirmation. Unknown provider outcomes require reconciliation before retrying.

Back to your workspace →