Skip to main content
POST
/
posts
curl --request POST \
  --url https://api.postiz.com/public/v1/posts \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "type": "schedule",
  "date": "2024-12-14T10:00:00.000Z",
  "shortLink": false,
  "tags": [],
  "posts": [
    {
      "integration": {
        "id": "your-integration-id"
      },
      "value": [
        {
          "content": "Hello world!",
          "image": []
        }
      ],
      "settings": {
        "__type": "bluesky"
      }
    }
  ]
}
'
[
  {
    "postId": "post-123",
    "integration": "integration-456"
  }
]

Documentation Index

Fetch the complete documentation index at: https://docs.postiz.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Post type: now, schedule, or draft

The top-level type field controls when (and whether) the post is published:
ValueBehaviour
"now"Publish immediately. date is ignored.
"schedule"Publish at the time given in date (ISO 8601).
"draft"Save as a draft. The post is created and stored against the integration but not scheduled or published. You can promote it to a real post later from the Postiz UI.
Drafts are how you stage content via the API without committing to a publish time — useful for content review workflows or pre-filling a calendar from an external CMS.

​
Duplicating a post

There is no dedicated duplicate / clone endpoint. To copy an existing post, fetch it with GET /posts and submit the content as a new POST /posts request. Before re-submitting, strip the server-managed fields from the fetched object — re-sending them either causes validation errors or, worse, accidentally updates the original. At minimum drop:
  • id and any nested post IDs
  • createdAt, updatedAt, and any other timestamps
  • state / status / releaseId (these are assigned by the scheduler)
  • Anything else the API didn’t ask you to provide when you originally created the post
Then set a fresh type (now, schedule, or draft) and date, and POST the cleaned object.

​
Provider-Specific Settings

When creating posts, each social media platform requires different settings. The settings object must include a __type field that identifies the platform.

​
All 27 Supported Platforms

Platform__typeRequired Settings
X (Twitter)xwho_can_reply_post (optional: community, made_with_ai, paid_partnership)
LinkedInlinkedin-
LinkedIn Pagelinkedin-page-
Facebookfacebook- (optional: url)
Instagram (FB-linked)instagrampost_type
Instagram Standaloneinstagram-standalonepost_type
Threadsthreads-
Blueskybluesky-
Mastodonmastodon-
Warpcast (Farcaster)warpcast- (optional: subreddit[] for channels)
Nostrnostr-
VKvk-

​
Platforms Without Custom Settings

These platforms only need the __type field: 
{
  "settings": {
    "__type": "threads"
  }
}
Platforms: threads, mastodon, bluesky, telegram, nostr, vk

​
Detailed Provider Settings

See the Provider Settings section for detailed schemas and examples for each platform.

Authorizations

​
Authorization
string
header
required

Your Postiz API key

Body

application/json
​
type
enum<string>
required

Post type

Available options:
draft,
schedule,
now
​
date
string<date-time>
required

Publish date in UTC ISO format

​
shortLink
boolean
required

Whether to use short links

​
tags
object[]
required
​
order
string

Order of posts

​
inter
number

Interval between posts

​
posts
object[]

Required if type is not 'draft'

Response

200 - application/json

Post created successfully

​
postId
string
​
integration
string