Agency, API-first

How a small agency runs 27 client accounts through the posterly API

A technology agency in India that handles social media for a mix of clients, including a cafe, a car dealer and a non-profit.

By , founder of posterly ·

How they postREST API
27
Accounts managed
900+
Posts in 2 months
7
Platforms

The challenge

An agency that already writes software does not want to copy and paste captions into a dashboard for every client. A social media API it can call from its own systems means every client, from a cafe to a car dealer to a non-profit, can be scheduled from one place, each with the right account.

How they set it up

Building something similar? The agencies page covers the workflow side of running several clients, and the API reference lists every endpoint with its request and response shapes.

1

One workspace, many client accounts

Each client's social accounts are connected to posterly, so the agency can address any of the 27 accounts directly while keeping every client separate.

2

Schedule through the REST API

The agency's own tooling calls the posterly REST API to create and schedule posts, so content can come from its own planning process instead of being retyped.

3

Cover the networks each client actually uses

Across the 27 accounts the agency publishes to 7 platforms: Bluesky, Facebook, Google Business, Instagram, LinkedIn, X and YouTube.

4

Keep the dashboard for review

Anything created through the API is visible in the dashboard, so the team can still check the calendar and fix a post by hand when needed.

What you need

  • A posterly workspace with each client's social accounts connected, ideally grouped by brand so every client stays separate.
  • An API key from Dashboard, API and MCP. A key acts as the person who created it, with that person's workspace role, and creating or rescheduling posts needs the Publisher role or higher.
  • The API and MCP add-on, which is a paid add-on on top of a plan. Its price depends on the plan, so check the pricing page.
  • Somewhere to run your own code, such as a script, a scheduled job or an internal tool. The API is plain HTTPS and JSON, so any language that can make a request will do.

Set up the same workflow yourself

These steps are written for you. They are general how-to guidance, not a record of what this customer did.

  1. 1

    Check the key

    Call GET /api/v1/whoami to see which user and scopes the key carries, then GET /api/v1/accounts to list every connected account with its ID and connection status.

  2. 2

    Map clients to accounts

    Keep each client's account IDs in your own system. GET /api/v1/brands returns the clients in the workspace, and GET /api/v1/brands/{id}/accounts returns the accounts assigned to one of them.

  3. 3

    Validate before you create

    Send the body you plan to schedule with dry_run set to true. The response says whether it is valid, shows the normalised post and lists any warnings, and it creates nothing.

  4. 4

    Create with a retry key

    Send POST /api/v1/posts with account_id, caption, scheduled_at and any media_urls. Add an Idempotency-Key header so a retry after a timeout returns the original post instead of creating a second one.

  5. 5

    Batch when you have many

    POST /api/v1/posts/batch takes a list of posts in one request. Items succeed or fail on their own: successes come back in posts and failures come back in errors with their index.

  6. 6

    Watch the results

    List posts with the status filter to find failures, and call GET /api/v1/posts/counts to see how many posts each client has in a given month. A webhook for post.failed can alert you as it happens.

What it can look like

Illustrations written for this page, checked against the API and MCP docs. They are not the customer's own prompts or code.

Example, not the customer's ownExample request: validate one post
curl -X POST https://www.poster.ly/api/v1/posts \
  -H "Authorization: Bearer pst_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "CLIENT_ACCOUNT_ID",
    "caption": "Your caption here.",
    "scheduled_at": "2026-12-01T09:00:00Z",
    "dry_run": true
  }'

Written for this page from the public API docs. Remove dry_run once the response looks right, and look up real account IDs with GET /api/v1/accounts.

Example, not the customer's ownExample body for POST /api/v1/posts/batch
{
  "posts": [
    {
      "account_id": "CLIENT_A_ACCOUNT_ID",
      "caption": "Caption for client A.",
      "scheduled_at": "2026-12-01T09:00:00Z"
    },
    {
      "account_id": "CLIENT_B_ACCOUNT_ID",
      "caption": "Caption for client B.",
      "scheduled_at": "2026-12-01T10:00:00Z"
    }
  ]
}

Batch requests do not accept dry_run, so validate each item on the single-post endpoint first.

Things to watch out for

  • A batch does not accept dry_run. Validate items one by one on the single-post endpoint, then send the batch.
  • Batch requests can partly succeed. Read the errors array, fix those items and resend only them under a new Idempotency-Key. Reuse the original key only when you resend the whole batch unchanged.
  • A key acts as the person who made it. If that person lacks the Publisher role, creating a post answers 403 with insufficient_workspace_permissions.
  • A key can be limited to one brand, so automation for one client cannot reach another client's accounts. Use that for anything client-specific.
  • Third-party media URLs are copied into posterly storage when the post is created, so a short-lived signed link must still work at that moment.
  • Batch posting, webhooks and OAuth clients are not available during a free trial. They unlock when the paid plan starts.

What you can copy

If your agency has any development capacity, the API turns social scheduling into just another step in your content workflow. Build a small script or internal tool that pushes approved posts to posterly, and you can add a new client account without adding a new manual process.

Platforms in this story

Related

Set up the same workflow

Start a free 7-day trial, connect your accounts and schedule your first posts today.

Card-backed 7-day trial. Cancel anytime.

FAQ

Common questions

Shared anonymously from real posterly account activity. Figures as of November 2026.