Post Results endpoints

Post Results aggregate successful publish events and failures for every target account on a post. Use them for dashboards, retries, and user-facing status.

Endpoints

• GET /api/v1/post-results — List results with post/platform filters.
• GET /api/v1/post-results/{id} — Fetch a single result.

GET /api/v1/post-results

Query filters:

• offset, limit — see pagination rules (applied after merging success + failure rows).
• post_id — array of post IDs.
• platform — array of platform IDs (twitter-x, instagram, linkedin, facebook-page, tiktok, youtube, bluesky, threads, pinterest).

Response:

{
  "data": [
    {
      "id": "result-uuid",
      "post_id": "post-uuid",
      "success": true,
      "social_account_id": "acc-123",
      "platform_data": {
        "id": "platform-owned-id",
        "url": "https://platform.com/post/123",
        "username": "syncpostly"
      },
      "error": null
    }
  ],
  "meta": { "offset": 0, "limit": 10, "total": 4 }
}

Failed rows set success: false, url: null, and include error:

{
  "error": {
    "code": "API_RATE_LIMIT",
    "message": "Rate limit exceeded",
    "context": { /* provider-specific */ }
  }
}

Results are sorted newest-first by event time before pagination.

Example:

curl "https://<host>/api/v1/post-results?post_id=post-uuid&platform=linkedin" \
  -H "Authorization: Bearer YOUR_SECRET_TOKEN"

GET /api/v1/post-results/{id}

Path: id (string). Returns either a success or failure record; 404 if the ID does not belong to the caller.

Notes

• social_account_id is null when the platform event could not be tied to a connected account (rare).
• Success rows pull the platform URL when available so you can link users to the live post.