REST · Bearer · OpenAPI

Blort API

Everything Blort does on the board, callable from your own code. Transcribe any post, run visual analysis, generate content, all through one API.

From key to first 200.

Standard REST. Standard Bearer auth. No SDK required.

01

Generate an API key

From your Blort workspace settings. Treat it like a password. Server-side only.

02

Send a Bearer-authenticated request

Header is Authorization: Bearer <key>. JSON in, JSON out.

03

Read the OpenAPI

Every route, parameter, and response shape is documented.

One curl, real output.

Drop your key in the env, run the command, parse the JSON.

Blort API /v1/transcribe

Request

curl -X POST \
  https://api.getblort.com/v1/transcribe \
  -H "Authorization: Bearer $BLORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://tiktok.com/@brand/video/123"}'

Response 200 OK

{
  "id": "[TRANSCRIPT_ID]",
  "platform": "tiktok",
  "duration": [SECONDS],
  "segments": [
    { "start": 0.0, "end": 2.4,
      "text": "[HOOK LINE]" },
    ...
  ]
}

A few routes that matter.

The full surface lives in the OpenAPI. Here's what most teams wire up first.

  1. POST/transcribe

    Drop in any TikTok, Reel, or YouTube link. Get back a clean, timestamped transcript.

  2. POST/generate

    Turn a transcript, image, or brief into platform-ready copy and captions.

  3. POST/analyze/visual

    Frame-by-frame breakdown: hooks, pacing, on-screen text, scene changes.

  4. POST/repurpose

    One piece in, versions out for TikTok, Reels, Shorts, LinkedIn, and Facebook Ads.

See every route in the OpenAPI

Same AI, callable from code