Schedule AI-produced content through the API and receive the result by webhook

Connect output from your existing AI tools and scripts to Ankk and follow the final provider state.

Connect the first API publish View developer guide

No credit card · 3 SNS channels free

Product workflow proof

Carry state from accepted to published

Follow the API request, queued operation, and signed webhook as one publishing job.

ANKK · MULTI-CHANNEL OPERATIONS

Ankk

AI and automation operators

Connected
Connected Scheduled Needs action Published Inbox
POST /v1/contents/publish
Authorization: Bearer <api_key>
Idempotency-Key: campaign-2026-08

{
  "scheduledFor": "2026-08-22T05:00:00Z"
}

202 accepted · operation_id: op_01

Accepted

webhook · op_01

Queued

webhook · op_01

Published

webhook · op_01

app.ankk.app

Where automation stops before publication

Submit content from external AI and scripts through the API and receive the result by webhook.

  • Content output and provider publication are disconnected
  • An accepted response is treated as a published post
  • Failures have no consistent result path

Capabilities for this workflow

The contract publishing automation needs

API and CLI input
Send an approved payload through Web, API, or CLI into the same publishing workflow.
Explicit states
Distinguish accepted, queued, publishing, published, and failed.
Signed webhooks
Receive final success and failure results at your endpoint.

From approved content to final publication

Submitting a request is not the same as publishing on the provider. Follow all three steps.

  1. 01

    Prepare approved content

    Review content written directly or prepared in an external AI tool or script.

  2. 02

    Schedule by channel

    Check supported formats and settings, then choose the publishing time.

  3. 03

    Verify final state and failures

    Inspect published, failed, and connection states and continue with the needed action.

Automation continues beyond request submission to the final publication result.

CLI/API

Move repeat publishing faster with CLI/API

Send content from the AI service or internal script you already use into Ankk CLI/API for scheduling, status tracking, and signed webhook results.

  • Create and schedule directly from the web dashboard
  • Connect repeatable work through CLI/API
  • Receive results with API keys and signed webhooks
Read the developer guide
$ bunx @anakonn/ankk --json health
$ ankk contents publish --file payload.json --scheduled-for "2026-07-01T09:00:00Z"
AI tools + Ankk

Use Codex, Claude Code, ChatGPT, or your automation stack

The AI tool writes, plans, or runs the workflow. Ankk receives the publishing request, schedules it, and keeps the operational status visible.

Each demo connects content from an external AI tool to Ankk scheduling and status tracking.

Via Codex

Plan in Codex, publish through Ankk

Turn a launch brief into channel-specific posts, then send them directly to Ankk scheduling.

Via Claude Code

Run CLI scheduling from the terminal

Let Claude Code prepare the command, review the payload, and submit content with ankk contents publish.

Via ChatGPT

Draft in ChatGPT, hand off to Ankk

Use ChatGPT for post ideas and refinement, then move approved copy into Ankk for scheduling and status tracking.

Via API automation

Wire scripts and no-code tools into publishing

Send accepted content into Ankk from scripts, schedulers, or automation tools while keeping webhook-driven status.

Automation

Track every request through the final publishing result

Request publishing with an API key, track processing status, and receive success or failure through signed webhooks.

API key

Connect securely with an API key

Free includes 1 API key and 500 API requests per 30 days. Growth includes API access subject to fair use.

Authorization: Bearer <api_key>
CLI command

Manage the same posts and states from the CLI

Request scheduled publishing from the terminal and check the same post results shown in the web dashboard.

ankk contents publish --file payload.json
Signed webhook

Receive results through signed webhooks

Free includes 1 webhook endpoint and 100 webhook deliveries per 30 days. Growth includes signed customer webhooks subject to fair use.

Failure visibility

Keep tracking after a request is accepted

Acceptance is only the start. Track queued, publishing, published, failed, and retry states through the final result.

Frequently asked questions

Connect the first automated publish

Use the Free API key and webhook allowance to verify the path from request to result.

Connect the first API publish View developer guide