1
Find the workspace you want to publish from
Every post is created inside a workspace. Start there so your requests always target the correct brand, team, or client.
Guide hub
Postly API guides for real publishing workflows
This page is built for implementation, not browsing. Find the exact posting pattern you need, understand the shape of the request, and then jump into the matching guide on docs.postly.ai for the final implementation details.
9
implementation patterns
4
guide categories
REST + SDK
compatible workflow ideas
Find the right pattern fast
Docs first, samples second
This page helps you choose the right scenario quickly. The official docs are the final guide for exact endpoint paths, field names, auth, limits, and platform behavior.
Start here
Quick path before you post anything
These three steps reduce most integration mistakes before you touch media, overrides, or scheduling, and they map directly to the core docs flow.
2
Fetch connected socials for that workspace
Use the social account ids returned by Postly. Those ids belong in target_platforms and keep your delivery precise.
3
Choose the right posting pattern
Pick the sample that matches your workflow, then adapt the payload for media, overrides, or scheduling.
Browse patterns
Searchable guide sections
Topics are grouped so this page stays usable as more workflows get added. Each scenario links out to the relevant docs guide for final implementation.
9 results4 sections
Setup and targeting
Setup and targeting
These patterns help you target the correct workspace and social accounts before you add scheduling or media.
3 guides
Setup and targetingWorkspaceSingle target
1 workspace, 1 channel target
Use one workspace and one target account when a request should publish to a single destination.
Fetch the workspace, fetch socials, then use that social id in target_platforms.
Request sample
These snippets are simplified examples. Use the linked docs pages as the final source of truth for current endpoints, required fields, auth, limits, and platform-specific behavior.
{
"text": "Post to one channel",
"workspace": "WORKSPACE_ID",
"target_platforms": [
{
"identifier": "facebook",
"id": "SOCIAL_ID"
}
]
}Setup and targetingWorkspaceMulti-channel
1 workspace, 3 channel targets
Publish one post from one workspace across multiple connected social accounts.
Fetch the workspace, fetch socials, then add each social id as a separate object in target_platforms.
Setup and targetingMulti-workspaceAgencies
3 workspaces, 3 separate LinkedIn posts
Use separate requests when different brands or clients live in different workspaces.
Fetch each workspace, fetch socials for each one, then create one separate post request for workspace A, one for workspace B, and one for workspace C.
Media and assets
Media and assets
Use these patterns when your posts need uploaded files, hosted assets, or channel-safe media payloads.
3 guides
Media and assetsUploadsImages
Upload files for images and videos
Upload media first, then attach the returned file URL in the post request.
Use the file endpoint when your app has a local image or video file. After upload, use the returned URL in the media array.
Media and assetsHosted mediaImages
Post with multiple image URLs
Attach more than one hosted image by adding multiple media objects in the media array.
Useful when your CMS, DAM, or media library already hosts the images and you want to send them directly by URL.
Media and assetsVideoMedia payload
Video post: keep it to one video per post
Use one video object in media for each post request to keep the payload channel-safe.
Keep the request simple: one video item in the media array for each post request.
Content modeling and overrides
Content modeling and overrides
Shape reusable content payloads when one campaign needs multiple channels, custom copy, or upstream systems.
2 guides
Content modeling and overridesJSONReusable payloads
Keep text content in a JSON file
Store reusable text, captions, and target metadata in JSON before sending the final request.
This is useful for generated content, scheduled content, approvals, and review workflows.
Content modeling and overridesOverridesCross-channel
Use platform-specific overrides
Keep one base post, then override text or media per platform when needed.
Useful when the same campaign needs slightly different copy or media for LinkedIn, Instagram, and Facebook.
Scheduling and workflow control
Scheduling and workflow control
Move from immediate publishing to planned releases, approvals, and queue-based distribution.
1 guide
Scheduling and workflow controlSchedulingCalendars
Schedule a post instead of publishing immediately
Use one_off_schedule for a date and time when your workflow needs delayed publishing.
Best for CMS workflows, approvals, content calendars, and queue-based publishing.