Docs · Using A1 Lane
How to prove a social post actually published
Short answer
A scheduler saying “sent” only proves that a request left. To prove a post is live, you have to ask the platform afterwards whether the post exists and who can see it, and keep that answer. A1 Lane does this for every destination: after publishing, it reads the post back from the platform and records what the platform said on a delivery receipt. Where a platform offers no way to read a post back, the receipt says Delivered (limited) and names what it has instead.
Three things that look like proof but aren't
- “Scheduled” or “sent” in a scheduler. That records an intention, or that a request left. The platform can still reject the post, hold it for processing, or publish it with a different visibility.
- A success response from the platform's API. For many platforms a successful create call means “accepted”, not “visible”. Video uploads in particular go through processing after the call returns.
- A post ID. An ID proves the platform created a record. It doesn't prove the record is public: a video can exist and be private.
What real proof looks like
| Question | Where the answer comes from |
|---|---|
| Does the post exist? | A read of the post by its ID, after publishing |
| Who can see it? | The visibility the platform reports on that read |
| Is it the post you meant? | What the platform reports, compared with what was sent |
| When was this checked? | The time of the read, kept with the record |
When the answer is “we can't tell”
Sometimes the publish request goes out and the answer never comes back. The post may or may not exist. A1 Lane marks this uncertain and never retries it automatically, because a retry could publish the post twice. A resolution probe looks for the post instead; if it can't decide, a person does.
Per platform: what the receipt can prove today
| Platform | Connectable today | What the receipt proves |
|---|---|---|
| YouTube | Yes | Checks the live post: We read the post back from the platform and record what it shows. Read-back via videos.list. |
| X | Yes | Checks the live post: We read the post back from the platform and record what it shows. |
| Yes, limited | Delivered (limited): No LinkedIn delivery has been confirmed end to end yet. LinkedIn accepts the post and returns its ID; the receipt records that response and doesn't claim the live post was checked. | |
| Bluesky | Yes | Checks the live post: We read the post back from the platform and record what it shows. Read back from the account's own PDS. |
| Mastodon | Yes | Checks the live post: We read the post back from the platform and record what it shows. Read back by status id. |
| Discord | Yes | Checks the live post: We read the post back from the platform and record what it shows. Verified by reading the message back through the same webhook (Get Webhook Message). |
| Telegram | Yes | Delivered (limited): Telegram has no read-back. The receipt records Telegram's own send response, and says so. |
| Instagram, TikTok, Facebook Pages, Pinterest, Threads | No, in platform review | Nothing yet: these can't be connected until each platform's review approves A1 Lane. |
Every platform's capabilities side by side: the platform matrix. How each receipt is confirmed: How each platform confirms a post. All delivery states: What your delivery status means. Connect one account and read your first receipt: Getting started. Real receipts: Real posts, real receipts.
Written against A1 Lane on 2026-11-11.