How do I connect Threads before I call the API?

Sign up for free, open a workspace, and choose Connect channel → Threads. Complete OAuth in the dashboard. OpenQuok Cloud registers the developer app for you. For self-hosted deployments, see the self-host Threads setup guide.

Where do I find the Threads integration UUID?

Call GET /public/integrations with your workspace programmatic token. Match the `identifier` field to `threads` and copy the channel UUID into `integrationIds`. Field tables for Threads live on Threads provider settings.

Can I schedule to Threads with one API request?

Yes. Send one POST /public/posts payload with the channel UUID in `integrationIds`. Set `scheduledAt` to an ISO-8601 UTC timestamp for the publish time. OpenQuok stores the instant in UTC and publishes when the worker dequeues the row. See Threads CLI examples for copy-paste recipes.

Does OpenQuok bill per Threads API call?

No. OpenQuok bills workspaces on paid plans, not per-post credits. Public API access requires a paid tier. Each opo_ token gets 30 requests per hour on OpenQuok Cloud. Scheduled posts still count toward your monthly post quota. See cloud limits.

Where can I test the Threads payload before I ship code?

Use the interactive Payload Wizard on this page with sample channels, or open the full wizard in your workspace after you sign in. Copy JSON stays free on public pages. Provider field reference: Threads settings. Channel landing: Threads.

Threads Scheduling API

Queue Threads posts and reply chains for a future publish time. Set scheduledAt in UTC with threads.replies and plug settings.

Get Started for Free Get Started for Free Get Started for Free

Try Payload Validator Try Payload Validator Try Payload Validator

The Getting Started Guide The Getting Started Guide The Getting Started Guide

Built for people who connect their own channels

Who schedules on, Threads via API?

Vibe coders

Connect your channels in OpenQuok Cloud. Complete OAuth in the dashboard. Then set scheduledAt with curl, the Node SDK, MCP, or CLI. UTC timestamps stay predictable in JSON. Schedule to Threads through the same request shape.

CLI and SDK users

Queue publish times in one REST call. OpenQuok delivers on the worker. You do not run cron per platform. Channel and post caps on your plan still apply. Schedule to Threads through the same request shape.

Agent operators

Ask your agent to schedule into your workspace. It uses the accounts you connected. It does not onboard other people’s customers onto your token. Schedule to Threads through the same request shape.

Three steps

Add Threads scheduling,to your product in three steps

Connect Threads once, then schedule posts and track delivery through the same API.

New to OpenQuok? Read the getting started guide

Payload preview

Sample channels

Post body

Launch post

Endpoint

POST /api/v1/public/posts

JSON payload

{
  "scheduledAt": "2026-01-01T12:00:00.000Z",
  "status": "scheduled",
  "body": "Launch post",
  "integrationIds": [
    "<integration-id>"
  ]
}

Free payload wizard

Test your social media scheduling API payload before you ship code

Compose a scheduled post with sample channels in your browser. Set publish time, document carousel names, follow-up comments, and optional repeat cadence, then copy the JSON body. Copy JSON is free — no account required. Scheduling and file uploads need a workspace.

Explore request and response examples by format

Static examples mirror shipped OpenQuok public API payloads and success responses.

Schedule a text on Threads. Set scheduledAt to an ISO-8601 UTC timestamp.

Request

JSON body

{
  "scheduledAt": "2026-01-01T12:00:00.000Z",
  "status": "scheduled",
  "body": "Launch post",
  "integrationIds": [
    "<integration-id>"
  ]
}

Response

JSON body

{
  "success": true,
  "data": {
    "postGroup": "9a0a1b2c-3d4e-4f5a-9b8c-aa11bb22cc33",
    "posts": [
      {
        "id": "5b3c1d2e-9a3f-4e6b-bb12-2c0a5f1a90a1",
        "state": "QUEUE",
        "publishDate": "2026-01-01T12:00:00.000Z",
        "organizationId": "c1d8a3f4-1234-4abc-bf12-1234567890ab",
        "integrationId": "1f9a4f3a-3b2c-4f4a-9d8e-7a3f6b1c8e22",
        "content": "Launch post",
        "delay": 0,
        "postGroup": "9a0a1b2c-3d4e-4f5a-9b8c-aa11bb22cc33",
        "title": null,
        "description": null,
        "parentPostId": null,
        "releaseId": null,
        "releaseUrl": null,
        "settings": null,
        "image": null,
        "intervalInDays": null,
        "error": null,
        "deletedAt": null,
        "createdByUserId": null,
        "createdAt": "2026-05-10T09:00:00.000Z",
        "updatedAt": "2026-05-10T09:00:00.000Z"
      }
    ]
  }
}

More social media scheduling API platforms

Compare Threads with other networks, or jump to platform docs and provider settings.

All Platforms' Rules Provider settings

Node SDK

TypeScript SDKfor Node.js backendstyped REST calls

Install @openquok/node-sdk in your Next.js or TypeScript backend. Call post() to schedule on Threads with the same JSON you send to POST /public/posts. scheduledAt, repeatInterval, and provider settings stay typed.

Get Started for Free Get Started for Free Get Started for Free

The Getting Started Guide The Getting Started Guide The Getting Started Guide

npm install @openquok/node-sdk

import Openquok from '@openquok/node-sdk';

const openquok = new Openquok('opo_your_programmatic_token');

await openquok.post({
  {
    "scheduledAt": "2026-01-01T12:00:00.000Z",
    "status": "scheduled",
    "body": "Launch post",
    "integrationIds": [
      "<integration-id>"
    ]
  }
});

# After you add OpenQuok in your MCP client config:
# Ask your agent to schedule on Threads.

> Schedule on Threads for tomorrow at 10am UTC:
> Product launch recap with a link to our pricing page.

MCP server

MCP toolsfor Cursor and Claude Codesame public API

Connect your MCP client with an opo_ token. Schedule Threads posts from chat with schedulePostTool and integrationList. Agents use the same REST API as curl and the SDK.

Get Started for Free Get Started for Free Get Started for Free

The MCP Setup Guide The MCP Setup Guide The MCP Setup Guide

OAuth2 for apps

OAuth2 appsuser consent workspace tokens

Register your app under Developers → Apps. Users approve access to their workspace, then your app calls the public API for Threads scheduling without pasted workspace keys.

Get Started for Free Get Started for Free Get Started for Free

The OAuth for Apps Guide The OAuth for Apps Guide The OAuth for Apps Guide

# Redirect the user to approve your app
https://www.openquok.com/oauth/authorize?client_id=oqc_your_client_id&response_type=code&state=random123

# Exchange the code for an opo_ access token, then call:
curl -H "Authorization: Bearer opo_oauth_access_token" \
  https://api.openquok.com/api/v1/public/integrations
# Match identifier: threads — copy id into integrationIds

Pricing

Transparent pricingfor Threads scheduling API

Every paid plan includes Public API access, MCP tools, and OAuth apps per workspace. Schedule on Threads via REST, Node SDK, or MCP — start with a 7-day free trial, no credit card required.

Solo

$29 / mo

Prototype Threads scheduling from curl, SDK, or MCP before you ship to customers.

Start for $0 Start for $0 Start for $0

Compare all features Compare all features Compare all features

Features

1 agent workspace
Total 15 channels
500 posts per month
Unlimited AI Writer (experimental)
Unlimited AI Summarizer (experimental)
Public API access
1 OAuth app
1 MCP server (same OAuth connection)
Total 5.0 GB cloud storage
Multi-channel publishing
Agent integrations

7-day free trial — no credit card required to start

Self-host for $0

OpenQuok charges no software fee when you run it on your own infrastructure. You still pay for servers, Supabase, and bandwidth.

Hosted cloud Docker Compose Cloud production stack Self-hosting overview

API examples FAQ