Introduction

The TryPost REST API lets scripts and integrations do what you do in the app: create, schedule and publish posts, upload media, manage channel queues and posting schedules, ideas, labels, signatures, webhooks and repurposes, and read analytics.

Base URL

https://app.trypost.it/api

Self-hosting TryPost? The API lives at your APP_URL followed by /api, for example https://trypost.yourdomain.com/api. Everything on these pages applies the same way.

Authentication

Every request sends a workspace API key as a Bearer token in the Authorization header:

curl https://app.trypost.it/api/workspace \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"

Always send Accept: application/json, as in every example on these pages. Without it, some errors (for example the 409 for a busy channel queue) come back as a redirect instead of a JSON body. Create a key in the app under Settings → API Keys → Generate API Key (see API keys), or with Create API key. The key is shown once, when it is created. Store it right away; if you lose it, generate a new one.

Treat an API key like a password. Do not put it in client-side code or commit it to a repository.

API keys authenticate the REST API only. The MCP server uses OAuth sign-in, and an MCP token sent to the REST API is refused with 403 Personal access token required..

Who can use API keys

API keys work only for workspace admins: the account owner and members marked as admin. When the key’s owner is not an admin of the workspace, every request returns 403 with Insufficient workspace permissions., and when they have left the workspace, 403 with Workspace access denied.. See Members and permissions.

One key, one workspace

A key is bound to the workspace it was created in. Every request acts on that workspace, whatever workspace you have open in the app, and resources of other workspaces answer 404. To automate several workspaces, create one key in each.

Approvals

Admins publish directly, so a post created or edited through the API is never held for approval: status: scheduled schedules it and status: publishing publishes it right away. Members who need approval still send requests from the app and the MCP server. Those posts show up in the API with status: pending_approval, and you can decide them with Approve post and Reject post. Get workspace returns your own permissions in me (is_admin, requires_approval, publishes_directly).

Subscription

On TryPost Cloud the workspace’s account needs an active subscription or trial. Without one, every request returns 402:

{
  "message": "Active subscription required."
}

Self-hosted installs have no billing, so they never return 402.

AI features

AI writing and image tools are part of the web app only. The API has no AI endpoint, and creating a post through the API never calls AI. A repurpose may shorten a caption that is too long for a destination with AI (see Create repurpose).

Rate limits

Each workspace can make 60 requests per minute. All keys of a workspace share that budget. Responses carry X-RateLimit-Limit and X-RateLimit-Remaining. Six calls that reach a network directly also count against a second limit of 60 requests per minute per user, shared by the six of them, by all your workspaces, and by the same lookups in the app (channel, board and music pickers): List Pinterest boards, Create Pinterest board, List Discord channels, Get TikTok creator info, Search Instagram audio and Get Instagram audio. Instagram audio also has its own limit of 30 uncached lookups per minute per workspace. Over the limit, the API answers 429 with a Retry-After header (seconds to wait):

{
  "name": "rate_limit_exceeded",
  "message": "Rate limit exceeded. Please retry after 30 seconds."
}

Errors

The API uses standard HTTP status codes and always answers JSON with a message.

Status	Meaning
`200`	Success
`201`	Created
`204`	Success with no body (deletes except Remove post recurrence, queue reorder)
`401`	Missing, invalid or expired API key (`Token expired.`)
`402`	Cloud only: no active subscription (`Active subscription required.`)
`403`	Not allowed: the key’s owner is not a workspace admin (`Insufficient workspace permissions.`), or the action is not allowed for this resource
`404`	The resource does not exist in this workspace
`409`	Another change to the same post or channel queue is in progress. Retry the request
`422`	Validation failed, or the action does not fit the resource’s state (for example, editing a post that was already published)
`429`	Rate limit exceeded

Validation errors list the messages of each field under errors, with the field path as key:

{
  "message": "Select a Pinterest board to publish this post.",
  "errors": {
    "meta.board_id": [
      "Select a Pinterest board to publish this post."
    ]
  }
}

On Create post and Update post the key is the field itself: meta.board_id, content_type, content, media. On Create posts in batch it names the destination, for example destinations.0.meta.board_id. Other errors carry only message:

{
  "message": "Insufficient workspace permissions."
}

Response shape

A single resource comes back as a plain object, with no data wrapper:

{
  "id": "9d3c1f2a-6b4e-4c8a-9f1e-2a7b5c8d0e41",
  "content": "We just shipped scheduled threads.",
  "status": "scheduled"
}

Lists are paginated (see below). A few responses have their own shape, documented on their page: List content types returns { "platforms": [...] }, List idea stages a plain array, List repurpose source formats { "data": [...] }, Create posts in batch { "posts": [...] }, and Create API key { "token": {...}, "plain_token": "..." }. Posts, notes, ideas, idea stages, labels, signatures and the workspace give their timestamps as Y-m-d H:i:s in UTC (2026-10-12 14:00:00). API keys, webhooks, webhook logs, repurposes, uploads, free queue slots and channel post performance use ISO 8601. In analytics, top posts use Y-m-d H:i:s; publication analytics and coverage use ISO 8601. In requests, send dates as ISO 8601 with an offset or Z (2026-10-12T14:00:00Z).

Pagination

Lists such as posts, ideas, labels, signatures, social accounts, API keys, webhooks, webhook logs, repurposes and post notes are paginated. Pick a page with the page query parameter:

curl "https://app.trypost.it/api/posts?page=2" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"

The server sets the page size; there is no per_page parameter. Read it from meta.per_page rather than assuming a number (it is 25 today). The response uses the standard envelope:

{
  "data": [
    { "id": "9d3c1f2a-6b4e-4c8a-9f1e-2a7b5c8d0e41", "...": "..." }
  ],
  "links": {
    "first": "https://app.trypost.it/api/posts?page=1",
    "last": "https://app.trypost.it/api/posts?page=3",
    "prev": "https://app.trypost.it/api/posts?page=1",
    "next": "https://app.trypost.it/api/posts?page=3"
  },
  "meta": {
    "current_page": 2,
    "from": 26,
    "last_page": 3,
    "path": "https://app.trypost.it/api/posts",
    "per_page": 25,
    "to": 50,
    "total": 72,
    "links": [
      { "url": "https://app.trypost.it/api/posts?page=1", "label": "&laquo; Previous", "page": 1, "active": false },
      { "url": "https://app.trypost.it/api/posts?page=1", "label": "1", "page": 1, "active": false },
      { "url": "https://app.trypost.it/api/posts?page=2", "label": "2", "page": 2, "active": true },
      { "url": "https://app.trypost.it/api/posts?page=3", "label": "3", "page": 3, "active": false },
      { "url": "https://app.trypost.it/api/posts?page=3", "label": "Next &raquo;", "page": 3, "active": false }
    ]
  }
}

Keep requesting links.next until it is null.

Next steps

Posting

Pick a channel, fill its settings, then schedule, queue or publish a post.

Media uploads

Upload files, attach them from URLs and reuse media across posts.

Overview

Posts

Post notes

Approvals

Recurrence

Media and uploads

Social accounts

Channels

Ideas

Idea stages

Analytics

Labels

Signatures

Workspace

API keys

Webhooks

Repurposes

Platform

Base URL

Authentication

Who can use API keys

One key, one workspace

Approvals

Subscription

AI features

Rate limits

Errors

Response shape

Next steps

Posting

Media uploads

​Base URL

​Authentication

​Who can use API keys

​One key, one workspace

​Approvals

​Subscription

​AI features

​Rate limits

​Errors

​Response shape

​Pagination

​Next steps

Posting

Media uploads

Base URL

Authentication

Who can use API keys

One key, one workspace

Approvals

Subscription

AI features

Rate limits

Errors

Response shape

Pagination

Next steps