DaypostSign in

Daypost API and MCP

Create a scoped key under Developer in your workspace. Send it as Authorization: Bearer <key> to either endpoint.

MCP

Use /api/mcp with Streamable HTTP in an MCP client that supports a custom Authorization header. Tools are listed according to your key’s permissions.

{
  "mcpServers": {
    "daypost": {
      "type": "http",
      "url": "https://mydaypost.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <DAYPOST_API_KEY>"
      }
    }
  }
}

REST API

These paths are relative to /api/v1. The REST API uses JSON, and each workspace can make up to 120 requests per minute.

Upload and schedule

  1. Call POST /media/uploads with { "name": "clip.mp4", "mime": "video/mp4", "bytes": 123456 }.
  2. PUT the raw bytes to the returned signed URL with the returned Content-Type. Send your API key only to Daypost.
  3. Call POST /media/{id}/complete. Attach its ID as mediaId in the post.
{
  "requestId": "<unique-uuid>",
  "caption": "Behind the scenes",
  "mediaId": "<media-uuid>",
  "scheduledAt": "2026-12-01T16:00:00Z",
  "destinations": [
    {
      "channelId": "<channel-uuid>",
      "options": {}
    }
  ]
}

Reuse requestId when retrying a schedule request. Omit scheduledAt to queue for the next worker run. YouTube requires a title, visibility and audience. TikTok requires the creator’s current privacy options, a preview and explicit consent.

Media retention

Uploads are temporary by default. Daypost deletes the private file after all deliveries finish and keeps the post history. Use retention: "library" for a reusable file. Unattached temporary uploads and files needed to review failed or unconfirmed deliveries are kept for at least 24 hours.