Post everywhere from your own code

What you can build

The API is the one the Octoque app itself uses, so anything you can do with a post in the app, a key can do too: the same caption limits, platform rules and plan allowances apply.

How it works

1. Upload the video or photo: POST /v1/media. Octoque checks the file by its contents and notes its length.
2. Create a draft for the accounts you choose: POST /v1/posts. Each account is a target with its own caption, options and time.
3. Send it: /schedule at a time you pick (or each platform's golden hour), /queue for your next free posting time, or /publish-now.
4. Check what happened: GET /v1/posts/{id} shows each platform's status, live link or a plain reason it didn't post, and /metrics shows results.

Your first request

This asks for the next golden hour on three platforms. It needs no special scope, so it's a good way to check a new key.

export OCTOQUE_API_KEY="oq_live_••••"

curl "https://api.octoque.com/v1/golden-hour?platforms=instagram,tiktok,youtube" \
  -H "Authorization: Bearer $OCTOQUE_API_KEY"

{
  "platforms": {
    "instagram": { "at": "2026-10-15T19:00:00+05:30", "hour": 19 },
    "tiktok":    { "at": "2026-10-15T20:00:00+05:30", "hour": 20 },
    "youtube":   { "at": "2026-10-15T18:00:00+05:30", "hour": 18 }
  },
  "activity": [2, 1, 1, …],
  "audience_regions": ["India"],
  "timezone": "Asia/Kolkata"
}

The times are starting points per platform, in your audience's time zone. How golden hour works.

Keys and scopes

• Made in the app by a workspace owner or admin, under You → Developers & AI. A key starts with oq_live_ and is shown once; Octoque keeps only a hash.
• Scoped. post.read reads, post.write makes and edits drafts, post.publish sends them, account.manage connects accounts. A key never has more than the person who made it.
• Walled off from your account. Keys can't change passwords, make keys, manage the team or billing, export data or delete the account. Those need a real sign-in.
• Easy to cut off. Revoke a key and everything using it stops at once. The list shows when each key was last used.

Full details, with every endpoint and its scope: API reference: scopes.

Plans and limits

• Request size: 1 MB for JSON, 1 GB per file.
• Request rate: no per-key quota today. If one is added, it will be documented first.
• Version: v1, in early access. Breaking changes go in the changelog before they ship.

This page was last updated on 17 October 2026.