Docs menu
Getting started

Taka API

REST API for generating, scheduling, and publishing social content across your connected channels. Everything Taka does in the app, generate, schedule, publish, brand, analytics, behind a scoped API key. Use it from scripts, cron jobs, or AI agents.

Building an AI agent?
Give it https://api.taka.ai/llms.txt for the whole surface in plain text, or install the taka-agent skill for Claude Code and Cursor. Taka also speaks MCP natively.

Base URL

base.url
https://api.taka.ai/v1/public

Machine-readable contract: openapi.json. This reference is generated from that spec at build time.

Quick start

1. Mint a key. In the app, open Business → API & MCP, grant only the scopes the task needs, and copy the key. It is shown once; Taka keeps only a hash.

2. Say hello. The account endpoint returns your business, plan, credits, and connected channels.

hello.taka
curl https://api.taka.ai/v1/public/account \
  -H "Authorization: Bearer taka_live_..."

3. Ship something. Create a draft, then generate it with AI. Generation draws 1 credit and returns a job to poll.

first.post
curl -X POST https://api.taka.ai/v1/public/posts \
  -H "Authorization: Bearer taka_live_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: first-post-1" \
  -d '{"platform": "instagram", "idea": "Weekend special: fresh croissants"}'
generate
curl -X POST https://api.taka.ai/v1/public/posts/POST_ID/generate \
  -H "Authorization: Bearer taka_live_..."

Typical workflow

  • Create a post with an idea and a primary platform.
  • Generate it; poll the job until the draft is ready.
  • Revise by prompt if needed; results carry honesty flags that say what changed.
  • Schedule it to a slot, or publish now. Outside review mode, a schedule ships the post when its slot arrives.
  • Read analytics later and draft the next one from what worked.

One post carries a variant per platform. Edit the primary and the other variants re-derive; edit a specific variant and it pins. Published content is immutable, create a new post instead.

Two things stay in the browser

Connecting a social channel (OAuth) and billing. Everything else, your code or your agent can do. See Taka for AI agents for the product tour of the agent surface.

Next steps