Blog API

I want to push content into my Inkie blog programmatically. My system has the content (titles, body, scheduled dates); Inkie owns the publishing pipeline. Here's everything you need:

## API

Base URL: https://app.inkie.ink

Auth: Bearer token in the Authorization header.
  Authorization: Bearer YOUR_API_KEY

### Option 1 — Create a blog from complete content I already have
POST /api/blogs/create
  Body: {
    platforms: ["wix"],                       // required, see /api/platforms for the list of yours
    scheduledDate: "2025-10-20T10:00:00",     // required, ISO datetime, LOCAL time (no tz suffix)
    title: "...",                             // required
    body: "<p>Full HTML body...</p>",         // required
    metaDescription: "Optional SEO description",
    clientId: 123,                            // optional, defaults to my account's active client
    contentPlanId: 456                        // optional, associate with a content plan
  }
  Response 200: { status: "SCHEDULED", blogId, planId }

### Option 2 — Have Inkie's AI generate the blog from a topic (async)
POST /api/blogs/generate
  Body: {
    platforms: ["wix"],
    scheduledDate: "2025-10-21T10:00:00",
    topic: "...",                             // required, the brief
    clientId: 123,
    contentPlanId: 456
  }
  Response 202: { status: "PROCESSING", blogId, planId, statusUrl: "/api/blogs/{blogId}/status" }

### Poll generation status (only needed after generate)
GET /api/blogs/{blogId}/status
  Response 200: {
    state: "PROCESSING" | "SCHEDULED" | "FAILED",
    progress: 0–100,
    steps: [{ name, state }, ...]
  }
  Poll every 3–5 seconds until state === "SCHEDULED".

### Retrieve a blog after creation
GET /api/blogs/{blogId}
  Response 200: { id, title, body, metaDescription, scheduledDate, status, platforms }

### Error shape
{ error: "..." }   // any non-2xx

## What I want you to build

1. A small helper module `inkie-blog-client.ts` (or equivalent for my language) exposing two functions:
   - `createBlog(input)` — wraps POST /api/blogs/create
   - `generateBlog(input)` — wraps POST /api/blogs/generate AND polls /status until completion (or surfaces FAILED), then fetches the final blog via GET /api/blogs/{id}

2. Both functions should:
   - Throw / return Result with the API's error message on non-2xx
   - Be small, dependency-free (use native fetch)
   - Read API key + base URL from environment variables (INKIE_API_KEY, INKIE_BASE_URL — default https://app.inkie.ink)

3. A worked example showing how to call `createBlog` from my existing content pipeline. Ask me where my content currently lives (CMS / Notion / Markdown files / etc.) so the example slots into MY shape, not a generic one.

## Critical details (Inkie-specific gotchas)

- `scheduledDate` is local time, NOT UTC. Pass "2025-10-20T10:00:00" — no `Z`, no tz offset. Inkie converts to UTC internally using my client's timezone setting.
- `platforms` accepts only platforms I've connected. Call GET /api/platforms first if unsure which strings are valid for my account.
- `generate` is async: response is 202 not 200, and the blog won't exist at /api/blogs/{id} until polling shows SCHEDULED.
- `body` for /create must be valid HTML. Markdown will publish as escaped HTML — convert first if your source is Markdown.

## Things to NOT do

- Don't poll /status faster than every 3 seconds — be a good citizen.
- Don't retry on 4xx errors — they're configuration mistakes, not transient.
- Don't hardcode the API key in source. Use env vars and document them in the README.

## Reference

Full docs: https://app.inkie.ink/docs/blog-api
OpenAPI spec: https://app.inkie.ink/api/openapi.json

Now ask me what language I'm working in (TypeScript / Python / Go / etc.) and where my content currently lives, then scaffold the helper module and worked example.

I want to integrate my Inkie blog into this site as a headless CMS feed. Inkie publishes my blog posts; my site fetches and renders them. Here's everything you need:

## API

Base URL: https://app.inkie.ink

Auth: Bearer token in the Authorization header.
  Authorization: Bearer YOUR_API_KEY

### List blogs
GET /api/client-blogs?page=1&perPage=20
  Optional query params:
    published (default true; pass false for unpublished/scheduled drafts — preview/staging only)
    search (substring match on title)
    scheduledFrom, scheduledTo (ISO dates)
  Response: { success: true, data: BlogSummary[], count, page, perPage }
  BlogSummary: { id, title, slug, metaDescription, publishedAt, scheduledDate,
                 status, excerpt, mainImage?: { id, url, alt, title },
                 readingTime }
  Cache: public, max-age=300 (5 min). Sort: newest first.

### Get a single published blog
GET /api/client-blogs/{blogId}
  Response: { success: true, data: BlogDetail }
  BlogDetail includes: title, slug, body (HTML string), pageTitle,
    metaDescription, publishedAt, scheduledDate, additionalImages[],
    structuredData (a ready-made schema.org/BlogPosting JSON-LD object),
    readingTime, wordCount.
  Cache: public, max-age=600 (10 min).

### Error shape
{ success: false, error: "..." }   // any non-2xx

## What I want you to build

1. A blog index page at /blog that:
   - Fetches GET /api/client-blogs?perPage=20 (server-side / at build time)
   - Renders a card grid with title, excerpt, mainImage.url, readingTime, publishedAt
   - Links each card to /blog/{slug}

2. A blog detail page at /blog/{slug} that:
   - Fetches GET /api/client-blogs/{id} (resolve slug → id via the list, or pass id in URL — whichever your router prefers)
   - Renders the body HTML directly (it's safe — sanitised on Inkie's side)
   - Adds the entire structuredData object into the page's <head> as:
       <script type="application/ld+json">{JSON.stringify(structuredData)}</script>
   - Sets pageTitle as the <title>, metaDescription as <meta name="description">
   - Optionally renders additionalImages somewhere in the layout

3. Style it to match the rest of the site. Use the site's existing typography + card components.

4. Where caching matters (Next.js ISR, Astro static fetch, Remix loader cache), respect Inkie's Cache-Control headers — don't fetch on every request.

## Things to NOT do

- Don't fetch on every page load — use ISR / static / loader-cache with a 5-10 min TTL
- Don't try to write through this API — it's read-only. Inkie creates blogs; you render them.
- Don't strip the structuredData — it's the SEO win, drop it into <head> exactly as returned.

## Reference

Full docs: https://app.inkie.ink/docs/blog-api
OpenAPI spec: https://app.inkie.ink/api/client-blogs/openapi.json

Now ask me which framework I'm using (Next.js, Astro, Remix, Nuxt, SvelteKit, plain HTML, etc.) and what URL my site lives on, then scaffold the two pages above.