---
title: "Delivery receipts for a post"
method: GET
path: "/post-results"
---

# Delivery receipts for a post

`GET /post-results`

## Request

- Base URL: `https://xpost.to/api/v1`
- URL: `https://xpost.to/api/v1/post-results`
- Auth: HTTP bearer

Also how a post is shown again: the reply carries `approval_url`, a signed link to the post as a picture of itself (caption, destinations, outcome), for every status — an already-decided post cannot be decided through it. Per-platform delivery receipts: each targeted account gets its own row with status, retries, the live post URL on success, or error detail on failure. A successful row may also carry `note`, with `note_kind` saying what it means: `"info"` — the post went out whole and the note only says how (the pin used the account's catch-all board because none was picked) — or null, meaning something was left behind (X takes 4 images, Facebook won't let an app post photos and video together, a reel is one clip). Check this after publish time and report honestly — including partial failures and any `note`. Don't re-post over an `info` note: nothing is missing.

## Query parameters

- `post_id` string, uuid, required

## Response `200`

Receipts

- object
  - `post_id` string
  - `post_status` string
  - `data` object[]

## Other responses

- `401`: Missing or invalid API key
- `404`: Post not found in this project
- `429`: Rate limited

---

[API](https://skmtc.dev/xpost/apis/xpost-api.md) · [All operations](https://skmtc.dev/xpost/apis/xpost-api/llms.txt) · [OpenAPI document](https://skmtc.dev/xpost/apis/xpost-api/revisions/9f570fcfed6d?raw)