PostSyncer Social Media Assistant

Autonomously manage social media through PostSyncer using the REST API.

Setup

1. 1. Create a PostSyncer account at app.postsyncer.com
2. Connect social profiles (Instagram, TikTok, YouTube, X, LinkedIn, etc.)
3. Go to Settings → API Integrations and create a personal access token with abilities: workspaces, accounts, posts, and (if you use them) labels, INLINECODE4
4. Add to .env: INLINECODE6

PostSyncer MCP (optional)

PostSyncer MCP uses the same Bearer token as REST. Typical tools: list-workspaces, list-accounts, post CRUD, list-media, get-media, upload-media-from-url, delete-media, list-folders, create-folder, get-folder, update-folder, delete-folder, comments, labels, campaigns, analytics.

Multipart file upload is only via REST: POST /api/v1/media/upload/file (not exposed as an MCP tool). Use upload-media-from-url or REST URL import when the client cannot send multipart.

How to Make API Calls

All requests go to https://postsyncer.com/api/v1 with the header:

CODEBLOCK0

Use web_fetch, curl, or any HTTP tool available. Always read $POSTSYNCER_API_TOKEN from the environment.

---

API Reference

Discovery (Call First)

List Workspaces — INLINECODE24

CODEBLOCK1

Returns workspaces with id, name, slug, timezone.

List Accounts — INLINECODE29

CODEBLOCK2

Returns accounts with id, platform, username, workspace_id.

---

Media library

Requires the posts ability. Responses include id, workspace_id, folder_id, and asset metadata.

List Media — INLINECODE38

CODEBLOCK3

Query params: workspace_id, folder_id, root_only (true/false), page, per_page (max 100).

Get Media — INLINECODE44

CODEBLOCK4

Import from URLs — INLINECODE45

CODEBLOCK5

Upload file (multipart) — INLINECODE46

Use multipart/form-data with fields such as workspace_id, file (and optional chunk/chunk metadata if your client uses chunked upload). Not JSON.

Delete Media — DELETE /api/v1/media/{media_id} (confirm first)

CODEBLOCK6

---

Media folders

Requires the posts ability.

List Folders — INLINECODE52

CODEBLOCK7

Query params: workspace_id, parent_id, root (top-level only).

Create Folder — INLINECODE56

CODEBLOCK8

Get Folder — INLINECODE57

Update Folder — INLINECODE58

CODEBLOCK9

Delete Folder — DELETE /api/v1/folders/{id} (confirm first)

---

Posts

List Posts — INLINECODE60

CODEBLOCK10

Query params: page, per_page (max 100), include_comments (true/false).

Get Post — INLINECODE64

CODEBLOCK11

Create Post — INLINECODE65

CODEBLOCK12

• - schedule_type: publish_now | schedule | INLINECODE69
• INLINECODE70: Optional scheduling object used when schedule_type is schedule. Provide {"date": "YYYY-MM-DD", "time": "HH:MM", "timezone": "..."} to schedule for a specific date/time, or omit/leave empty to auto-schedule to the next available time slot
• INLINECODE74: Array of thread items. Each needs text and/or media: an array of library media IDs (integers) and/or HTTPS URL strings (import or list media first when you want stable IDs)
• INLINECODE77: Array of {id, settings?}. Platform-specific options go in INLINECODE79

Update Post — INLINECODE80

CODEBLOCK13

Only posts that have not been published yet can be updated.

Delete Post — DELETE /api/v1/posts/{id} (confirm with user first)

CODEBLOCK14

---

Comments

List Comments — INLINECODE82

CODEBLOCK15

Query params: post_id (required), per_page, page, include_replies, platform.

Get Comment — INLINECODE88

CODEBLOCK16

Create Comment / Reply — INLINECODE89

CODEBLOCK17

Optional media: array of integer library IDs and/or HTTPS URLs (same shape as post content[].media; do not use a deprecated media_urls field).

Update Comment — INLINECODE93

CODEBLOCK18

Hide Comment — INLINECODE94

CODEBLOCK19

Delete Comment — DELETE /api/v1/comments/{id} (confirm first)

CODEBLOCK20

Sync Comments from Platforms — INLINECODE96

CODEBLOCK21

---

Labels

List Labels — INLINECODE97

CODEBLOCK22

Get Label — INLINECODE98

Create Label — INLINECODE99

CODEBLOCK23

Update Label — INLINECODE100

Delete Label — DELETE /api/v1/labels/{id} (confirm first)

---

Analytics

All analytics endpoints require the posts API ability.

All Workspaces — INLINECODE103

CODEBLOCK24

By Workspace — INLINECODE104

CODEBLOCK25

By Post — INLINECODE105

CODEBLOCK26

By Account — INLINECODE106

CODEBLOCK27

Sync Post Analytics — INLINECODE107

CODEBLOCK28

Queues background jobs to refresh metrics. Does not return metrics directly — call GET after sync.

---

Account Management

Delete Account — DELETE /api/v1/accounts/{id} (destructive, confirm first)

CODEBLOCK29

---

Platform-Specific Settings

Pass per-platform options in accounts[].settings when creating/updating posts:

Pinterest: INLINECODE110

X/Twitter:
CODEBLOCK30

TikTok:
CODEBLOCK31

Instagram: {"post_type": "POST"} — options: REELS, STORIES, INLINECODE114

YouTube:
CODEBLOCK32

LinkedIn: {"visibility": "PUBLIC"} — options: PUBLIC, CONNECTIONS, INLINECODE118

Bluesky: INLINECODE119

Telegram: {"disable_notification": false, "protect_content": false}

---

Common Workflows

Schedule a Post to Multiple Platforms

1. 1. GET /api/v1/workspaces → get INLINECODE122
2. INLINECODE123 → get ids for target platforms
3. Optionally POST /api/v1/media/upload/url (or MCP upload-media-from-url) → use returned ids in INLINECODE128
4. INLINECODE129 with schedule_type: "schedule" and INLINECODE131

Reply to Comments

1. 1. GET /api/v1/posts → find post INLINECODE133
2. INLINECODE134 with INLINECODE135
3. INLINECODE136
4. INLINECODE137 with post_id and optional INLINECODE139

Check Performance

1. 1. GET /api/v1/analytics/posts/{id} for a specific post
2. If stale: POST /api/v1/analytics/posts/{id}/sync, then re-fetch

---

Best Practices

• - Always start with GET /workspaces and GET /accounts to discover IDs; use GET /folders and GET /media when organizing or attaching library assets
• New automations: Use schedule_type: "draft" or confirm before INLINECODE147
• Destructive actions: State what will happen, confirm before delete operations
• Multi-network: One post can target multiple accounts; check per-platform status in the response
• Rate limits: 60 requests/minute — don't call sync endpoints repeatedly
• Hashtags: Keep relevant and limited (3–5 per post)

---

Error Handling

Status	Meaning
INLINECODE149	Token missing or invalid
INLINECODE150

Token lacks required ability (e.g. posts) | | 404 | Resource not found or no access | | 422 | Validation error — check required fields and formats | | 429 | Rate limited — wait before retrying |

---

Links

• - API Documentation
• PostSyncer Dashboard
• API Authentication