Introduction

Welcome to the Publer Public API. This RESTful JSON API brings Publer’s social media scheduling, publishing, and analytics capabilities into your own applications, scripts, or services. Whether you’re automating campaigns, building dashboards, or integrating content workflows, the Publer API provides the same power you know from the Publer web platform.

What is Publer?

Publer is an all-in-one social media management solution. From a single dashboard you can:

• Schedule and publish posts

• Manage accounts and team workspaces

• Track performance with built-in analytics

Supported networks: Facebook, Instagram, Twitter/X, LinkedIn, Pinterest, YouTube, TikTok, Google Business Profile, WordPress, Telegram, Mastodon, Threads, Bluesky.

What can I do with the Publer API?

• Create, schedule, and publish posts (text, images, videos, links, polls, carousels, PDFs)

• Upload, organize, and reuse media assets (images, videos, GIFs, documents)

• Automate workspace, account, and permission management

• Retrieve post

• Build custom integrations, dashboards, or bots

API Specifications

Authentication

Include your API token in every request header:

Authorization: Bearer-API YOUR_API_TOKEN
Publer-Workspace-Id: YOUR_WORKSPACE_ID // Required on special cases
Content-Type: application/json

Manage and regenerate tokens in Dashboard → Settings → API Keys.

Getting Started

1. Generate an API key in your Publer Dashboard.

2. Validate your credentials:

   Copy

   curl -H "Authorization: Bearer YOUR_API_TOKEN" \
        https://app.publer.com/api/v1/me

Support & Resources

If you need assistance with the API:

Jump right in

Retrieve profile, subscription, and application settings for the currently authenticated user. Use this endpoint to adapt your integration to user preferences and entitlements.

Requirements

• Authentication: Bearer API token

• Scope: users

• Headers:

  • Authorization: Bearer-API YOUR_API_KEY

Endpoint

Get Current User

GET /api/v1/users/me

Related Resources

Manage organizational units (“workspaces”) that group social accounts, members, and content. Workspaces help agencies, brands, and departments keep clients and campaigns separate under a single Publer login.

Requirements

• Authentication: Bearer API token

• Scope: workspaces

• Headers:

  • Authorization: Bearer-API YOUR_API_KEY

Endpoint

List Workspaces

Retrieve all workspaces accessible by the authenticated user.

GET /api/v1/workspaces

Working with Workspaces

• A user can belong to multiple workspaces.

• Each workspace has its own accounts, posts, and settings.

• Use the workspace context (Publer-Workspace-Id header) to target API calls at the correct workspace.

Workspace Context for Other Endpoints

Many endpoints require you to specify which workspace you’re operating in. Include the Publer-Workspace-Id header:

curl -X GET https://app.publer.com/api/v1/accounts \
  -H "Authorization: Bearer-API YOUR_API_KEY" \
  -H "Publer-Workspace-Id: 61a7c2e4f9e8c3b2d1e0f9a8"

Related Resources

To keep our service reliable and fair, the Publer API enforces rate limits on all requests. Limits are applied per user account (across all API keys) and use a sliding-window algorithm.

Default Limits

Tracking Your Usage

When you reach the rate limits, every API response includes these headers so you can monitor your rate limit status:

Example Response Headers

When You Exceed the Limit

If you go over your quota, the API returns:

• HTTP Status: 429 Too Many Requests

• Response Body:
• Headers will show X-RateLimit-Remaining: 0 and a future X-RateLimit-Reset.

Best Practices to Avoid Throttling

• Cache responses for idempotent or infrequently changing endpoints.

• Use bulk endpoints (e.g., POST /api/v1/posts/schedule for multiple posts).

• Stagger non-urgent requests during off-peak hours.

• Monitor headers and throttle your client.

• Implement exponential backoff when you approach or hit the limit.

Requesting Higher Limits

For integrations requiring a higher rate limit, please contact us with:

• Your expected request volume (per minute/hour/day)

• Use case description and critical endpoints

• Project or company name and contact info

Remove one or multiple posts—of any state—from your workspace. This endpoint enforces role-based permissions and state-specific restrictions.

Requirements

• Authentication: Bearer API token

• Scope: posts

• Headers:

  • Authorization: Bearer-API YOUR_API_KEY

  • Publer-Workspace-Id: YOUR_WORKSPACE_ID

Endpoint

DELETE /api/v1/posts

Deletes one or more posts based on the provided IDs.

Query Parameters

Authorization Rules

• You may delete:

  • Posts you created

  • Posts in workspaces you own

  • Posts in workspaces where you have “post action” access

• Private drafts: only their creator can delete

• Published posts requiring approval: restricted roles (e.g., editors) cannot delete

• Queued posts (except reminders): cannot be deleted

Pending-state deletions trigger a notification to the creator before removal.

Related Resources

Each social network offers unique post formats. Publer’s API supports these specialized types—click a format to dive into its implementation details:

Best Practices

• Choose the Right Format Select the layout that matches your content goal and platform norms.

• Follow Platform Guidelines Observe character limits, aspect ratios, and file-size rules.

• Enhance Engagement Interactive formats (polls, carousels) tend to drive higher user interaction.

• Test & Iterate Experiment across formats to discover what resonates best with your audience.

Related Topics

What Is the Publer API?

A RESTful JSON interface for automating social media workflows—scheduling, publishing, media management, and analytics—across multiple networks.

Base URL

All endpoints share this root URL:

Authentication

Include your API key and workspace ID on almost every request:

Request Format

GET

Use query parameters for filters and pagination:

POST, PUT, PATCH

Send JSON in the request body:

DELETE

No request body is required (unless otherwise noted):

Response Format

All responses are JSON.

Success

• Synchronous endpoints return the requested resource or collection.

• Asynchronous endpoints (e.g., post creation) return a job_id:

Error

• Status codes indicate general error type (4xx, 5xx).

• The response body contains an errors array:

Common HTTP Status Codes

• 200 OK

• 201 Created

• 202 Accepted (async)

• 400 Bad Request

• 401 Unauthorized

• 403 Forbidden

• 404 Not Found

• 429 Too Many Requests

• 500 Internal Server Error

Versioning

Asynchronous Operations

1. Submit your request → 202 Accepted + {"job_id": "…"}

2. Poll the job status endpoint until complete:

Date & Time

All timestamps use ISO 8601 with timezone:

Example: 2025-05-04T14:58:35+00:00

Privacy & Security

• Always use HTTPS.

• Sensitive fields may be redacted.

• Adhere to least-privilege scope selection.

Next Steps

For implementation examples, see the Quickstart Guide and sections on creating content, media handling, and network-specific formats.

Manage and retrieve social media accounts connected to your Publer workspaces. Use these accounts as targets when scheduling or publishing content.

Requirements

• Authentication: Bearer API token

• Scope: accounts

• Headers:

  • Authorization: Bearer-API YOUR_API_KEY

  • Publer-Workspace-Id: YOUR_WORKSPACE_ID

Endpoint

List Accounts

Retrieve all social media accounts in a workspace.

Retrieves a list of all social media accounts available in the specified workspace.

The list of accounts returned will include all social media accounts that you have connected to your Publer workspaces and have permission to access. These accounts can be used to schedule and publish content via the Posts API.

The accounts data provides important information about the social media profiles available for posting, including their configuration settings and current synchronization status.

Supported Providers

Publer supports these network providers and account types:

Related Resources

Create, manage, and publish draft posts that aren’t sent immediately. Drafts can be private (only you) or shared with your workspace for review and scheduling.

Endpoint

Use the same scheduling endpoint—with a draft state—to save work-in-progress content without publishing.

Creating Drafts

Set the state to one of the following:

Private Draft Example

Workspace Draft Example

Best Practices

• Save Often: Persist drafts early to avoid data loss.

• Collaborate: Use draft_public for workspace feedback and approvals.

Related Topics

Every Publer API request must include a valid API key. This guide shows you how to obtain, use, and manage your keys securely.

Obtaining an API Key

2. Navigate to Settings → Access & Login → API Keys.

3. Click Create API Key.

4. Enter a descriptive name for your key.

5. Select only the scopes your integration needs (e.g., posts, media, accounts).

6. Click Create.

7. Copy and securely store the key — you won’t see it again.

Using Your API Key

Include your key in the Authorization header for every request. Also provide your workspace ID:

Authorization: Bearer-API YOUR_API_KEY  
Publer-Workspace-Id: YOUR_WORKSPACE_ID  
Content-Type: application/json

Example (list posts):

curl -X GET https://app.publer.com/api/v1/posts \
  -H "Authorization: Bearer-API YOUR_API_KEY" \
  -H "Publer-Workspace-Id: 5f8d7a62c9e77e001f36e3a1"

API Key Scopes

When creating an API key, you must select specific permission scopes based on your integration needs:

Common Authentication Errors

• 401 Unauthorized • Missing or invalid Authorization header • Key revoked or expired

• 403 Forbidden • Insufficient scopes for the endpoint • Missing Publer-Workspace-Id header

Always inspect the JSON error response for message and code.

Security Best Practices

• Environment Variables Store your key outside code—e.g., in a .env file:

  Copy

  PUBLER_API_KEY=your_api_key_here

• Secrets Management Use a vault (AWS Secrets Manager, Azure Key Vault, HashiCorp Vault).

• Key Rotation Rotate keys every 90–180 days, or after team changes/incidents.

• Least Privilege Create separate keys for different use cases.

• Safe Logging Never log full keys; mask all but the last 4 characters:

  Copy

  console.log(`Using key ***${apiKey.slice(-4)}`);

• Always HTTPS Never send keys over plain HTTP.

Troubleshooting

If you continue to see authentication errors:

1. Confirm your key is active and not expired.

2. Verify you have the correct header names and values.

3. Double-check that your key has the required scopes.

Related Documentation

The Media API lets you list and filter items in your library. You can page through results, query by IDs, or apply filters such as type, usage status, source, labels, and search terms.

Requirements

• Authentication: Bearer API token

• Scope: media

• Headers:

  • Authorization: Bearer-API YOUR_API_KEY

  • Publer-Workspace-Id: YOUR_WORKSPACE_ID

Endpoint

List Media

Retrieve all social media accounts in a workspace.

GET /api/v1/media

Query Parameters

Notes

• Free trial users see placeholder data unless they supply specific query filters.

• Paid accounts have full library access.

Related Resources

Automatically append a branded or informative signature to your social posts. Signatures help drive consistency and professionalism across your accounts.

Overview

A signature is a reusable block of text (such as a disclaimer, call-to-action, or branded tagline) you can attach to posts on supported networks. You can manage multiple signatures per account and select which one to append when scheduling or publishing.

Step 1: Fetch Available Signatures

Before attaching a signature to your post, retrieve the available signatures for your account(s):

Step 2: Create or Schedule a Post with a Signature

When scheduling or publishing a post, use the signature parameter within the relevant accounts object to append a signature to the post.

Example Request:

{
  "bulk": {
    "state": "scheduled",
    "posts": [
      {
        "networks": {
          "facebook": {
            "type": "status",
            "text": "Check out our latest news!"
          }
        },
        "accounts": [
          {
            "id": "63c675b54e299e9cf2b667ea",
            "scheduled_at": "2025-06-13T10:16:00+02:00",
            "signature": "680fa73ebd7195d33da6630b"
          }
        ]
      }
    ]
  }
}

Parameters

Key Notes & Limitations

• Account-specific: Up to 10 signatures per account.

• Supported Networks: Most networks except Twitter/X and Bluesky (unless you have X Premium, due to character limits).

• Photo Captions: On Facebook, configure whether the signature is included in photo captions for multi-photo posts.

• Auto-Share: Signatures are not included when you auto-share a scheduled post.

• Signature Management: Signatures must be created and managed for each social account individually.

Best Practices

• Craft signatures that reinforce your brand identity.

• Use signatures for legal disclaimers, campaign CTAs, or promotional blurbs.

• Set a default signature for frequent use.

Related Topics

A comprehensive overview of all content formats you can publish via the Publer API. Each content type is specified by the type field inside the networks.[provider] object.

Supported Content Types

Best Practices

Content Optimization

• Test each format on a single account before scaling.

• Use network-specific overrides to tailor text length, captions, and metadata.

• Always provide alt_text for images to enhance accessibility.

• Follow each platform’s style and character limits for optimal engagement.

Technical Considerations

• Preprocess media (resize, compress) before upload to meet platform requirements.

• Verify media upload success before referencing media IDs in your post payload.

• Review provider documentation for specific limits (e.g., LinkedIn document size, TikTok clip length).

• Poll the job status endpoint to ensure the content was processed and published without errors.

Related Topics

This guide walks you through the core steps to integrate with Publer’s API in minutes. By the end, you’ll have published your first scheduled post.

Prerequisites

• A Top Publer Ambassador or Enterprise account

• Basic familiarity with HTTP/JSON APIs

• A command-line tool (curl) or API client (Postman, Insomnia)

Step 1: Generate an API Key

1. Sign in to Publer and verify you have Ambassador or Enterprise access.

2. Go to Settings → Access & Login → API Keys.

3. Click Create API Key.

4. Enter a descriptive name, then select scopes:

   • workspaces

   • posts

   • accounts

   • users

   • media

   • job_status

   • locations

5. Click Create.

6. Copy and store the key securely—this value will not be shown again.

Step 2: List Workspaces

Before making other requests, let's retrieve your workspaces. The workspace ID is required in the header for most API operations:

Sample Response

Now you can use a workspace ID in your subsequent requests by including it in the header:

Step 3: List Social Accounts

Next, let's retrieve the social media accounts in your workspace. You'll need the account IDs to specify where to publish your posts:

Expected Response

Make note of the account IDs as you'll need them to specify where to publish your content in the next step.

Step 4: Create a Scheduled Post

Make your first scheduled post with one API call:

Sample Response

The API returns a job ID that you can use to check the status of your request:

Step 5: Poll Job Status

Posts are created asynchronously. Use the returned job_id to check progress:

Successful Job Response

Failed Job Response

If there's an error with your request, the response will include details about what went wrong:

Step 6: Verify Scheduled Posts

List your scheduled posts to confirm creation:

Sample Response

Understanding the Workflow

1. Generate an API key

2. List workspaces → pick a workspace ID

3. List accounts → pick account IDs

4. Submit a post creation request

5. Poll job status until completed

6. Fetch posts to verify

This async pattern scales across multiple workspaces, accounts, and post types.

Next Steps

Publish content to social networks instantly using the Publer API. This method skips scheduling and sends posts for immediate delivery.

Endpoint

Request Headers

Request Body

Use the standard bulk structure. Omit scheduled_at under accounts:

Key Fields

• state: must be "scheduled" for immediate publishing

• networks: per-network content configuration (facebook, twitter, linkedin, etc.)

• accounts: list of target account IDs (no scheduled_at timestamp)

Sample Request

Sample Response

Status: 200 OK

Use the returned job_id to poll /api/v1/job_status/{job_id} until status: "completed".

Important Considerations

• Delivery Timing

  • Posts are sent as soon as Publer processes the request.

  • Network-side processing may introduce slight delays.

  • Job remains in working state until all targets confirm receipt.

• Platform Requirements

  • All network-specific content rules still apply (e.g., character limits, media formats).

  • Some networks may perform additional reviews before public display.

  • Ensure the connected accounts have immediate-posting permissions.

Common Issues

Related Topics

Schedule posts for future publication across one or more social networks using the Publer API.

Endpoint

Request Headers

Request Body

Include a valid ISO 8601 scheduled_at timestamp under each account:

Sample Request

Sample Response

Status: 200 OK

Key Fields

• state Must be set to "scheduled" for future publishing.

• accounts[].scheduled_at ISO 8601 timestamp (with Z or offset) specifying when to publish.

• networks Per-platform content configuration (e.g., facebook, twitter, linkedin).

Important Considerations

Time Formats

• Use full ISO 8601 format, including timezone (e.g., 2025-06-01T09:00:00+02:00).

• Timestamps must be at least 1 minute in the future.

Scheduling Limits

Best Practices

• Buffer Time: Space posts 1–2 minutes apart to avoid collisions.

• Timezone Awareness: Schedule using your audience’s local time.

• Batch Scheduling: Combine related posts in a single request for efficiency.

• Verify: Poll /api/v1/job_status/{job_id} to confirm scheduling success.

Related Topics

Manage and retrieve Facebook albums, Pinterest boards, and saved watermarks for your social accounts—all within your workspace. Use these options to organize content and protect your creative assets.

Overview

Media options help you:

• Organize your Facebook photos into albums.

• Pin to specific Pinterest boards.

• Protect your images and videos with custom watermarks.

Retrieve all available albums/boards and watermarks per account to use in your post scheduling workflows.

Fetch Media Options

Use the following endpoint to list all available albums (for Facebook), boards (for Pinterest), and saved watermarks for the accounts in your workspace.

Parameters

How to Use Media Options

• Facebook Albums: Select an album ID when posting to Facebook to keep your photos organized and easy to browse.

• Pinterest Boards: Use the board ID to specify where your Pin should be published.

• Watermarks: Choose a watermark ID to apply a logo, copyright, or brand mark to your images/videos. Watermarks help deter unauthorized use and reinforce your brand.

Related Topics

Simple yet powerful status updates without media attachments. Text posts are widely supported, versatile, and often drive high engagement.

Overview

Text posts (status updates) let you share plain-text messages across all major social networks. With the Publer API you can:

• Publish or schedule text updates simultaneously to multiple platforms

• Customize each network’s copy to match character limits and conventions

• Leverage network-specific features: hashtags, mentions, rich formatting

Key Features

• Cross-Platform Publishing Send consistent or tailored copy to every network in one API call.

• Character Limit Handling Automatic enforcement of each platform’s text length.

• Rich Text Support Use hashtags, emojis, and markdown styling where supported.

• Flexible Scheduling Instant publish, scheduled posts, or auto-optimized time slots.

Platform Support & Limitations

Request Structure

Below is an example showing a text post scheduled for multiple platforms:

{
  "bulk": {
    "state": "scheduled",
    "posts": [
      {
        "networks": {
          "facebook": {
            "type": "status",
            "text": "Exciting news! We're launching our new product line next week. #NewLaunch #ProductAnnouncement"
          },
          "twitter": {
            "type": "status",
            "text": "Big announcement coming next week! Our new product line is almost here 🚀 #NewLaunch #ProductAnnouncement"
          },
          "linkedin": {
            "type": "status", 
            "text": "We're thrilled to announce our new product line launching next week. Stay tuned for more details! #NewLaunch #ProductAnnouncement"
          }
        },
        "accounts": [
          {
            "id": "account_id_for_facebook",
            "scheduled_at": "2025-05-20T14:30:00Z" // Optional, depending on publishing method
          },
          {
            "id": "account_id_for_twitter",
            "scheduled_at": "2025-05-20T15:00:00Z" // Optional, depending on publishing method
          },
          {
            "id": "account_id_for_linkedin",
            "scheduled_at": "2025-05-20T16:00:00Z" // Optional, depending on publishing method
          }
        ]
      }
    ]
  }
}

Required Parameters

Best Practices

• Optimize per Platform Tailor messaging length and tone: concise on Twitter, detailed on LinkedIn.

• Use Hashtags Strategically Add relevant tags to boost discoverability; match platform conventions.

• Schedule for Peak Times Publish when your audience is most active across time zones.

• Include Clear CTAs Encourage engagement with direct calls-to-action.

• A/B Test Variations Schedule multiple text variants to measure which resonates best.

Related Topics

Animated GIFs are a fun, engaging way to capture attention. Use the Publer API to create or schedule single‐GIF posts with caption and thumbnail support across multiple platforms.

Overview

GIF posts let you share looping animations with optional captions and metadata. Perfect for reactions, announcements, or adding personality to your feed.

Key Features

• Cross-Platform GIF Publishing

• Custom Caption Support

• Thumbnail Preview

• Immediate or Scheduled Posting

Platform Support & Limits

Request Structure

Send to the scheduling endpoint (/posts/schedule) or immediate‐publish (/posts/schedule/publish):

POST /api/v1/posts/schedule
{
  "bulk": {
    "state": "scheduled",
    "posts": [
      {
        "networks": {
          "facebook": {
            "type": "gif",
            "text": "Check out this fun GIF!",
            "media": [
              {
                "id": "external",
                "type": "gif",
                "url": "https://media.giphy.com/media/xyz/giphy.gif",
                "path": "https://media.giphy.com/media/xyz/giphy.gif",
                "thumbnail": "https://media.giphy.com/media/xyz/200w.webp",
                "name": "Fun Reaction GIF"
              }
            ]
          }
        },
        "accounts": [
          { 
            "id": "ACCOUNT_ID", 
            "scheduled_at": "2025-08-02T23:18:00+02:00" 
          }
        ]
      }
    ]
  }
}

Required Parameters

Workflow

2. Build your post object with "type": "gif".

3. (Optional) Add "thumbnail" and "name" for preview.

4. Call /posts/schedule or /posts/schedule/publish.

5. Monitor /api/v1/job_status/{job_id} for completion.

Best Practices

• Compress GIFs to meet platform size limits without sacrificing quality.

• Provide a clear, engaging thumbnail to boost click-through.

• Use concise captions to add context or calls-to-action.

Related Topics

Tag your posts with a real-world location to increase engagement and reach more local audiences. Publer supports location tagging for Facebook Pages and Instagram Business accounts.

Overview

Location tagging attaches a physical place (such as a city, office, or venue) to your Facebook or Instagram post. This is especially helpful for businesses, events, and local marketing.

Step 1: Search for a Location

Use Publer’s dedicated endpoints to search and select the correct location for your post:

Location Object Example:

{
  "id": "308281375929281",
  "name": "Tirana",
  "info": "Tirana, Albania ⋅ 590 follow this",
  "verified": true,
  "address": "Tirana, Albania",
  "checkins": 590
}

Step 2: Schedule or Publish a Post with a Location

When creating or scheduling a post, use the location object inside the relevant accounts array:

Example Request:

{
  "bulk": {
    "state": "scheduled",
    "posts": [
      {
        "networks": {
          "facebook": {
            "type": "status",
            "text": "Facebook location"
          }
        },
        "accounts": [
          {
            "id": "63c675b54e299e9cf2b667ea",
            "scheduled_at": "2025-06-14T10:21:00+02:00",
            "location": {
              "id": "308281375929281",
              "name": "Tirana",
              "info": "Tirana, Albania ⋅ 590 follow this",
              "verified": null,
              "address": "Tirana, Albania",
              "checkins": "590"
            }
          }
        ]
      }
    ]
  }
}

Parameters

Key Notes & Limitations

• Supported Networks: Location tagging is supported for Facebook Pages and Instagram Business accounts only.

• Media Types Restrictions: You cannot add locations to Facebook regular videos, GIFs, Stories, or Reels scheduled via reminders.

• Other Networks: Twitter/X no longer supports location tagging via API.

• Search Required: Always search and select the correct location using the endpoints above before scheduling your post.

Best Practices

• Always verify the location by name and address before tagging.

• Tagging your business or event location can boost local discovery and engagement.

• Use location tags for promotions, events, or posts relevant to specific regions

Related Topics

Protect your creative content and reinforce your brand by automatically applying watermarks to photos and videos you share across your social accounts.

Overview

A watermark is a logo or symbol placed on your media to discourage unauthorized use and promote your brand. With Publer, you can save, manage, and apply unique watermarks per account—no editing skills required.

Watermarking is available on the Professional Plan for images and the Business Plan for videos.

Step 1: Fetch Available Watermarks

Response Example:

• Each watermark is account-specific.

• You can create and manage multiple watermarks per account in Publer.

Step 2: Schedule or Publish a Post with a Watermark

When creating or scheduling a post, specify the full watermark object in the relevant accounts array. The watermark settings will be applied to all attached media.

Example Request:

Parameters

Best Practices

• Use PNG logos with transparent backgrounds for cleaner results.

• Place watermarks in corners with moderate opacity to protect without distracting.

• Watermarking is available per account and per post—choose the right watermark for each audience.

Key Notes & Limitations

• Plan Requirements: Watermarking images requires the Professional Plan, videos require the Business Plan.

• Unlimited Media: No limit on the number of photos you can watermark per post.

• Account-specific: Watermarks are managed and applied per account.

• Media Orientation: Watermarks are applied consistently regardless of image/video orientation.

Related Topics

Create and schedule interactive polls on LinkedIn, Mastodon, and Twitter to engage your audience and gather feedback.

Key Features

• Cross-Platform Polls: One payload to post polls on multiple networks

• Flexible Duration: Support for platform-specific duration limits

• Option Constraints: Enforce character limits and unique choices

• Scheduling: Publish immediately or at a specified time

Supported Platforms & Limits

Tip: When sending a multi-network poll, adhere to Twitter’s 25-character option limit and common duration (e.g., 1, 3, 7 days).

Request Structure

Use the unified scheduling endpoint:

Parameters

Platform-Specific Notes

Twitter/X

• Options live in options array; question must be in text.

• 2–4 options, ≤25 characters each.

• Cannot edit after publishing.

LinkedIn

• Uses separate question and text.

• Options ≤30 characters.

• Up to 14-day duration.

Mastodon

• Question goes in text.

• Options ≤50 characters.

• Poll can be edited after posting.

Best Practices

• Keep questions clear and concise.

• Use unique, contrasting options.

• Align durations with campaign timelines.

Related Topics

Create and schedule multi‐link carousel posts on Facebook Pages. Carousels let you showcase up to 10 clickable cards—each with its own image, title, description, and call-to-action—in a single organic post.

Request Body

Parameters

networks.facebook

sublinks[] Object

Key Notes & Limitations

• Pages Only: Supported on Facebook Pages. Group posts will include only the first sublink.

• Max Sublinks: Up to 10 cards per carousel.

• No Cost: Carousel posts are organic (no ad spend).

• Syncing: Published carousel posts can only sync back as regular link posts (no carousel structure).

Workflow

1. Select Page Choose a Facebook Page account in the accounts array.

2. Define Sublinks Provide url, title, description, and images for each card.

3. Arrange Order Order sublinks as they should appear (array index defines order).

4. Schedule or Publish

   • For scheduled: set scheduled_at under accounts.

   • For immediate: omit scheduled_at and use /posts/schedule/publish.

Best Practices

• Engaging Thumbnails Use high-quality images that clearly represent each link.

• Clear Titles & Descriptions Keep text concise and action-oriented to drive clicks.

• Focused Carousels Limit to 5–7 cards to avoid overwhelming users.

• A/B Test CTAs Experiment with LEARN_MORE, SIGN_UP, and other button types.

Related Topics

Visual content that drives engagement across social networks. Use photo posts to share high-quality images—single or multiple—while respecting each platform’s unique requirements.

Key Features

• Multi-Platform Publishing Post images simultaneously to all supported networks.

• Multiple Image Support Single photos or carousels (up to platform limits).

• Advanced Customization Captions, alt text, and location tags where available.

• Resolution Optimization Automatic resizing and format handling per network.

Platform Support & Limits

Request Structure

Below is an example showing a photo post scheduled for multiple platforms.

Omit scheduled_at for immediate posts.

Required Parameters

* Omit scheduled_at when publishing immediately.

Media Workflow

2. Receive IDs: Note each media object’s id.

3. Compose Post: Reference those IDs in your media array.

4. Publish/Schedule: Send the payload to the posts endpoint.

Best Practices

• Optimize Quality: Compress and resize images to platform specs.

• Descriptive Alt Text: Enhance accessibility and SEO.

• Tailor Captions: Adjust tone and length per network.

• Experiment Carousels: Test image order to boost engagement.

• Consistent Branding: Use uniform styles and watermarks.

Related Topics