Posts

List posts across all customers via API

GET /merchants/posts returns the posts of all your customers at once, most recent first, using only the merchant token. It is the monitoring view: where posts failed, what was published and for which customer.

The request

GET /api/merchants/posts?status=failed&per_page=50
Authorization: Bearer <merchant token>

What you can do

  • List the posts of all customers in one call, with no x-customer-token.
  • Filter by one customer with customer, or by one connection with customer_integration.
  • Filter by status (created, publishing, published, failed) to find failures.
  • Find a post by your system's id with external_reference.
  • Paginate with per_page, from 1 to 100.

Rules and limits

  • Only the merchant Bearer, with no x-customer-token. For one customer's posts, use GET /posts with the x-customer-token.
  • customer and customer_integration are filters, not credentials: the customer and the connection are checked against the Bearer's merchant.
  • Filters combine. The list comes most recent first, 15 per page by default.
  • Each post carries customer_uuid, so you know which customer it belongs to.

Main fields

FieldTypeRequiredDescription
customerstringNoFilter: the uuid of one of the merchant's customers.
customer_integrationstringNoFilter: the uuid of a connection of one of the merchant's customers.
statusstringNoFilter: created, publishing, published or failed.
external_referencestringNoFilter: the post's id in your system (up to 100 characters).
per_pageintegerNoItems per page, from 1 to 100. Default 15.
customer_uuidstringNoOn each post in the response: the customer that owns the post.

Who it is for

  • Operations dashboard

    The support team sees every failed post from every customer on one screen, without querying customer by customer.

  • Failure alerts

    A periodic job lists status failed and notifies the owner of each account.

  • Monitoring AI agent

    The agent summarizes the week's publishing per customer and highlights the ones that failed most.

Works with

  • Instagram Business
  • Facebook
  • Threads
  • LinkedIn
  • Pinterest
  • YouTube

Frequently asked questions

Do I need the x-customer-token?

No. This route uses only the merchant Bearer. GET /posts, per customer, requires the x-customer-token.

How do I see just one customer?

Pass customer with the customer's uuid, or customer_integration with the connection's uuid.

How do I find the failed posts?

Filter by status=failed. For the error details, read the post with GET /posts/{uuid}.

Related

See everything you can do with Posts

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.