Posts
Track the status of a publication via API
Publishing with Connect is asynchronous: POST /posts responds 202 and the post goes to the network afterwards. To get the result, read the post by uuid or list the customer's posts with filters. The response carries the status, the link of the published post and the reason for a failure.
The request
GET /api/posts/<post uuid> Authorization: Bearer <merchant token> x-customer-token: <customer token>
What you can do
- Read a post with GET /posts/{uuid} and see status, permalink and the publishing state.
- List the customer's posts with GET /posts, filtering by customer_integration, external_reference and status.
- See the state of each media item in the publishing of each media entry.
- Get the post's link on the network in permalink and the network's id in publishing.external_id, once published.
- Find the post by your system's id, filtering by external_reference.
Rules and limits
- POST /posts responds 202 with the post in created. Check until status is published or failed.
- A post's status is created, publishing, published or failed. publishing.status details the progress and includes partially_published.
- When it fails, publishing.error carries code and message. Branch on code, never on the message.
- GET /posts returns the customer's posts, most recent first, with per_page from 1 to 100 (default 15). It requires the x-customer-token.
- To see the posts of all customers at once, use GET /merchants/posts, with only the Bearer.
Main fields
| Field | Type | Required | Description |
|---|---|---|---|
| uuid | string | No | The post's id in Connect, returned by POST /posts. |
| external_reference | string | No | The post's id in your system. Also filters GET /posts. |
| status | string | No | created, publishing, published or failed. Also filters GET /posts. |
| permalink | string | No | The post's link on the network, once published. |
| publishing.status | string | No | The publishing state: pending, processing, ready, publishing, published, partially_published or failed. Each media item has its own publishing. |
| publishing.error | object | No | Filled in when it failed: code and message. Branch on code, not on the message. |
| publishing.external_id | string | No | The id the network gave the post. |
| customer_integration | string | No | GET /posts filter: the connection's uuid. |
| per_page | integer | No | Items per page in GET /posts, from 1 to 100. Default 15. |
Who it is for
Publishing dashboard
The product shows each post as queued, published or failed, and the permalink as soon as it exists.
Reprocess failures
A job lists posts with status failed, reads publishing.error and notifies the customer or retries with another external_reference.
AI agent confirming delivery
The agent publishes, checks the post until status is published and only then gives the user the post link.
Works with
Instagram Business
Facebook
Threads
LinkedIn
Pinterest
YouTube
Frequently asked questions
How do I know the post went out?
Read GET /posts/{uuid} until status is published or failed. With published, permalink carries the post's link on the network.
How do I find a post by my system's id?
Use GET /posts with external_reference, which is the post's id in your system. You can also filter by status and customer_integration.
What does failed mean?
The publication was not completed. publishing.error carries the code and message of the reason.
See Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
