Build on AI Kraft

The public API gives third-party tools — Zapier, n8n, custom scripts, your own backend — programmatic access to AI Kraft's content generation, history, repurpose engine, and brand profiles. Every endpoint speaks JSON, authenticates with a bearer token, and returns standard HTTP status codes.

Authentication

Every request must include an Authorization header with your API key as a bearer token.

bash
Authorization: Bearer kraft_sk_aBcDeFgHiJk...

Each key has a list of permissions that gate which endpoints it can call:

• generate — call POST /generate
• read:history — call GET /history
• repurpose — call POST /repurpose
• read:brand — call GET /brand
• publish — reserved for future direct-publish endpoints

Rate limits

Limits are per-workspace, not per-key. Multiple keys for the same workspace share the same bucket.

Hitting the limit returns 429 Too Many Requests with Retry-After, X-RateLimit-Limit, and X-RateLimit-Remaining headers.

Endpoints

json
{
  "topic": "Launch our new jollof rice delivery service",
  "platform": "Instagram",
  "toneLevel": 3,
  "brandProfileId": "clx..."     // optional — defaults to your default brand
}

json
{
  "post": {
    "id": "clx...",
    "topic": "Launch our new jollof rice delivery service",
    "platform": "Instagram",
    "content": "Lagos, your weeknight just got SAVED...",
    "status": "DRAFT",
    "createdAt": "2026-06-05T01:23:45.000Z"
  }
}

json
{
  "posts": [ { "id": "clx...", "topic": "...", "platform": "...", "content": "...", "status": "DRAFT", "createdAt": "..." } ],
  "nextCursor": "clx..."
}

json
{
  "sourceContent": "Long-form blog post text here...",
  "platform": "LinkedIn",
  "toneLevel": 4,
  "brandProfileId": "clx..."
}

json
{
  "content": "After 18 months of building...",
  "platform": "LinkedIn"
}

json
{
  "brands": [
    { "id": "clx...", "brandName": "Mama Cass Cuisine", "industry": "Food & Beverage", "market": "nigeria", "isDefault": true, "voiceAnalysedAt": "2026-06-01T...", ... }
  ]
}

Code samples

The simplest possible call — generating an Instagram post — in three languages:

JavaScript / Node

javascript
const res = await fetch("https://aikraft.app/api/v1/generate", {
  method: "POST",
  headers: {
    "authorization": `Bearer ${process.env.KRAFT_API_KEY}`,
    "content-type": "application/json",
  },
  body: JSON.stringify({
    topic: "Friday night specials are live",
    platform: "Instagram",
  }),
});
const { post } = await res.json();
console.log(post.content);

Python

python
import os, requests

res = requests.post(
    "https://aikraft.app/api/v1/generate",
    headers={
        "Authorization": f"Bearer {os.environ['KRAFT_API_KEY']}",
        "Content-Type": "application/json",
    },
    json={
        "topic": "Friday night specials are live",
        "platform": "Instagram",
    },
)
post = res.json()["post"]
print(post["content"])

cURL

bash
curl -X POST https://aikraft.app/api/v1/generate \
  -H "Authorization: Bearer $KRAFT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "topic": "Friday night specials are live",
    "platform": "Instagram"
  }'

Webhooks

Subscribe a URL to receive events from AI Kraft. Useful for piping new posts into Slack, your CMS, or any tool that can receive an HTTPS POST.

Available events:

• post.created — fires when a new Post is saved (API or dashboard)
• credits.low — fires when wallet credits drop below 5

Payload shape

json
{
  "event": "post.created",
  "workspaceId": "clx...",
  "occurredAt": "2026-06-05T01:23:45.000Z",
  "data": {
    "post": {
      "id": "clx...",
      "topic": "...",
      "platform": "Instagram",
      "content": "...",
      "status": "DRAFT",
      "createdAt": "..."
    }
  }
}

Verifying signatures

Every POST includes an x-kraft-signatureheader — HMAC-SHA256 of the raw body, keyed with your webhook's secret. Reject any request whose signature doesn't match.

javascript
import crypto from "crypto";

// In your webhook handler:
const signature = req.headers["x-kraft-signature"]?.replace(/^sha256=/, "");
const expected = crypto
  .createHmac("sha256", process.env.KRAFT_WEBHOOK_SECRET)
  .update(rawBody)
  .digest("hex");

if (signature !== expected) {
  return res.status(401).send("bad signature");
}

Zapier setup walkthrough

AI Kraft works with Zapier via two patterns — incoming webhooks for triggers, and the public API for actions. No dedicated Zapier app yet; both patterns work today with Zapier's generic "Webhooks by Zapier" and "Custom Request" steps.

Trigger: "When a post is created in AI Kraft"

1. In Zapier, create a new Zap with the Webhooks by Zapier trigger.
2. Choose the Catch Hook event. Zapier gives you a URL like https://hooks.zapier.com/hooks/catch/123/abc/ — copy it.
3. In AI Kraft, go to Settings → Developer → Outbound webhooks. Click New webhook.
4. Paste the Zapier URL, name it (e.g. "Zap — Slack notify"), tick the post.created event, click Create.
5. Save and copy the signing secret if your Zap needs to verify it (most simple flows skip verification).
6. Back in Zapier, click Test trigger. Generate a post in AI Kraft — Zapier should pick it up within seconds.

Action: "Generate content from a row in Sheets"

1. Trigger on a new row in Google Sheets (or whatever source you prefer).
2. Add a Webhooks by Zapier → Custom Request action step.
3. Method: POST · URL: https://aikraft.app/api/v1/generate
4. Headers: Authorization: Bearer YOUR_KRAFT_API_KEY · Content-Type: application/json
5. Body (JSON): { "topic": "{{topic from sheet}}", "platform": "Instagram" }
6. Test the step — Zapier shows the generated post in the response.
7. Pipe the response into any downstream action: post to Slack, save back to Sheets, send via email, etc.