import { ParagraphAPI } from "@paragraph-com/sdk"

const api = new ParagraphAPI({ apiKey: "your-api-key" })
const draft = await api.content.create({
  kind: "tweet",
  title: "Thread on writing in public",
  body: { tweets: ["Writing in public changes what you write.", "Here's what changed for me."] },
})

{
  "id": "<string>",
  "kind": "<string>",
  "title": "<string>",
  "excerpt": "<string>",
  "status": "draft",
  "scheduled": true,
  "lockedReason": "<string>",
  "publishedAt": "<string>",
  "url": "<string>",
  "archivedAt": "<string>",
  "createdAt": "<string>",
  "updatedAt": "<string>",
  "body": {}
}

{
  "success": false,
  "msg": "<string>"
}

{
  "success": false,
  "msg": "<string>"
}

{
  "success": false,
  "msg": "<string>"
}

{
  "success": false,
  "msg": "<string>"
}

content

Create a draft

Save a finished piece of short-form content — an X post or thread, a LinkedIn post, a one-off email, or an X Article — to your publication’s library.

What this does:

The piece is saved as a draft and shows up in the Paragraph app under Content, where you can edit it and send it.
Nothing is posted, emailed, or scheduled. Sending happens in the app, so a draft you upload can’t go out without you.
Long-form Paragraph posts are a different resource — use POST /v1/posts for those.

The body:

body carries the artifact itself, in the shape its kind uses (see the field descriptions below).
It’s validated the same way the Paragraph app validates it, so an X thread over 280 characters an entry, or an Article missing its headline, comes back with the same explanation you’d see in the app.
Drafts created here are text-only. Media has to be uploaded to X or LinkedIn first, which the API can’t do yet.

POST

content

import { ParagraphAPI } from "@paragraph-com/sdk"

const api = new ParagraphAPI({ apiKey: "your-api-key" })
const draft = await api.content.create({
  kind: "tweet",
  title: "Thread on writing in public",
  body: { tweets: ["Writing in public changes what you write.", "Here's what changed for me."] },
})

{
  "id": "<string>",
  "kind": "<string>",
  "title": "<string>",
  "excerpt": "<string>",
  "status": "draft",
  "scheduled": true,
  "lockedReason": "<string>",
  "publishedAt": "<string>",
  "url": "<string>",
  "archivedAt": "<string>",
  "createdAt": "<string>",
  "updatedAt": "<string>",
  "body": {}
}

{
  "success": false,
  "msg": "<string>"
}

{
  "success": false,
  "msg": "<string>"
}

{
  "success": false,
  "msg": "<string>"
}

{
  "success": false,
  "msg": "<string>"
}

Authorizations

Authorization

string

header

required

API key for authenticating protected endpoints. Pass as Bearer token in Authorization header.

Body

application/json

Body

kind

enum<string>

required

What kind of piece this is

Available options:

tweet,

linkedin,

newsletter,

x_article

title

string

required

What this piece is called in your library. Sentence case, no trailing period. Not published anywhere — for an X Article headline, use body.title.

Required string length: 1 - 200

body

object

required

The artifact itself, in the shape this kind uses

Show child attributes

Response

Draft created successfully

string

required

Unique identifier for this piece of content

kind

string

required

What this piece is: tweet, linkedin, newsletter, or x_article

title

string

required

What this piece is called in your library

excerpt

string

required

First readable line of the body, for listing views

status

enum<string>

required

Whether this piece has been delivered, is still a draft, or was archived

Available options:

draft,

published,

archived

scheduled

boolean

required

Whether a scheduled send is queued against this piece

lockedReason

string | null

required

Why this piece can't be edited right now, or null when it can. A queued or in-flight send locks the words, because they go out exactly as written.

publishedAt

string | null

required

ISO 8601 timestamp of the first delivery, or null

url

string | null

required

Where this piece went live, from the same delivery publishedAt came from. Null when it hasn't been delivered, and null by design for a channel that publishes no page: a custom email renders into the message itself, so there is no address to link to. Never guessed — a delivery whose id isn't shaped like its channel reports null rather than a link that would 404.

archivedAt

string | null

required

ISO 8601 timestamp of when this piece was archived, or null

createdAt

string

required

ISO 8601 timestamp of creation

updatedAt

string

required

ISO 8601 timestamp of the last change

body

object

required

The artifact itself, in the shape its kind uses

Show child attributes

⌘I

publications

posts

content

me

users

coins

subscribers

discover

analytics

emails

auth

Create a draft

Authorizations

Body

Response