Getting Post Results

When you create a Post in Post for Me, you often target multiple social accounts and platforms simultaneously. To give you granular insight into the outcome of every specific publish attempt, we separate the concept of a Post from a Post Result.

Here is a breakdown of how to track the status of your content and debug issues using Post Results.

One Post, Multiple Results

A single Post entity acts as the container for your content, while Post Results represent the actual publication events on each platform.

How it works

If you create one Post that targets Instagram, Facebook, and LinkedIn, the system will generate three separate Post Results.

• Availability: Each individual result is made available via the API as soon as that specific platform accepts or rejects the content.

• Parent Status: The main Post entity remains in a processing status until every single targeted account has returned a result. Once all results are in, the Post status updates to processed.

Using Webhooks

While you can poll the API for updates, we highly recommend using Webhooks to receive real-time notifications when your content goes live.

How it works

By setting up a webhook, your application can listen for specific events to trigger immediate updates in your UI.

• social.post.result.created: Triggered immediately when a specific platform finishes processing (e.g., Facebook finishes, but Instagram is still loading).

• social.post.updated: Triggered when the parent Post status changes (e.g., moves from processing to processed).

This allows you to show "Published to Facebook!" checks instantly, rather than making the user wait for all platforms to finish.

Understanding the Outcome

Each Post Result contains detailed data fields to help you verify success or troubleshoot failures.

The Data Structure:

• Success: A simple boolean (true/false) indicating if the publish attempt worked.

• Error: If success is false, this field provides a general error message explaining why the post failed (e.g., "Image aspect ratio not supported").

• Details: For deeper debugging, this field contains the full log of every request and response exchanged with the social platform. This is critical for developers needing to understand exactly why a platform rejected a specific payload.