Media Upload

Boring does not require you to upload files to a dedicated endpoint. Instead, you reference media by URL in the mediaUrls field of the Publishing API. Boring fetches the media, runs any required processing (compression, format checks, async status polling), and hands it off to the target platform.

How to reference media

Pass one or more publicly reachable URLs in post.content.mediaUrls. The field accepts either a single string or an array:

{
  "post": {
    "accountId": "uuid-string",
    "content": {
      "text": "Hello world",
      "mediaUrls": ["https://cdn.example.com/photo.jpg"],
      "platform": "facebook"
    },
    "target": { "targetType": "facebook" }
  }
}

Supported URL sources

Google Drive: paste the normal share URL (e.g. https://drive.google.com/file/d/FILE_ID/view). Boring resolves it via the Drive API, with an HTTP-download fallback and magic-byte file-type detection.

Media count → post type

The number of media URLs determines the post type per platform:

For full per-platform request examples, see Publishing API.

Per-platform limits

Processing & async status

• Instagram, Threads, X, and TikTok process media asynchronously. Boring polls the platform's status endpoint automatically and only returns once the media is ready (or fails). No action needed on your side.
• Instagram Reels: videos larger than ~95 MB are re-encoded with ffmpeg before upload to stay within Instagram's limits.
• YouTube: uploads use a resumable session; large files are streamed server-side.

Optional fields

Tips

• Use direct, stable URLs — Boring downloads the media at publish time, so the URL must still be reachable then.
• Prefer standard formats: JPEG/PNG for images, MP4 (H.264/AAC) for video.
• For scheduled posts, the media URL must remain valid until the scheduled publish time.