Docs · Using A1 Lane
How each platform confirms your post
Short answer
A1 Lane records what each platform confirms after a post is sent. Some platforms let us check the post afterward; others only confirm the send. The receipt shows which kind of confirmation we have.
What a receipt can say
- Verified live
- We checked the platform after sending and found this post there.
- Delivered (limited)
- The platform accepted this post. See the receipt for what A1 Lane could and couldn't confirm. It is always followed by the one reason that applies.
- Couldn't publish
- Nothing was published to this account.
- Unconfirmed
- The platform didn't confirm whether this post published. It may be live. Check the platform before sending again.
A missing reply alone does not prove failure. If the receipt is Unconfirmed, check the platform before trying again.
All seven statuses: What your delivery status means. See dated test results by platform.
YouTube
How we confirm it
A1 Lane checks the video's status after YouTube finishes processing it, and records the visibility YouTube reports. A custom thumbnail, when set, is confirmed after the video and named on the receipt; it can never fail the delivery.
If confirmation is missing
A1 Lane checks the existing upload and never starts a second one.
Worked example
You schedule a video as Public. The upload finishes and YouTube returns a video ID: the receipt shows the upload accepted. Processing ends and the read reports privacyStatus: public: the receipt shows Verified live, visibility asked Public, visibility observed Public. View the YouTube test record
Technical references
Publish: a resumable upload through the YouTube Data API; the upload session is the anchor, and one session completes at most once. Confirm: videos.list on the new video ID, polled through processing, then read for its status, including privacyStatus.
X
How we confirm it
A1 Lane reads the post back from X.
If confirmation is missing
The receipt says Unconfirmed, and A1 Lane looks for a matching recent post instead of posting again.
Technical references
Publish: media upload in chunks (initialize → append → finalize), then POST /2/tweets; the media ID is saved so a retry never re-uploads. Confirm: GET /2/tweets/:id. Lost response: a scan of your recent posts for the same text in the same time window.
LinkedIn (personal profiles)
You can connect a personal profile.
How we confirm it
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. The receipt says Delivered (limited). To check it yourself, choose Open on LinkedIn on the receipt. It opens the post on LinkedIn, so you can see it there.
If confirmation is missing
The receipt says Unconfirmed. Whether A1 Lane can look for the post automatically depends on the permissions LinkedIn grants; otherwise a person checks.
Technical references
Publish: video upload in parts (images through LinkedIn's Images API), then POST /rest/posts; LinkedIn returns the post URN. Read-back: GET /rest/posts/{urn} needs r_member_social, a permission LinkedIn grants only on approval, which A1 Lane does not request; until then the receipt rests on the create response. The create call has no idempotency key.
Bluesky
How we confirm it
A1 Lane checks your account's server for the post.
If confirmation is missing
A1 Lane checks whether the original was created: found means Verified live; not found means it wasn't created.
Technical references
Publish: a record created in your repository under a record key A1 Lane mints itself, so the same post can't be created twice under two keys. Confirm: com.atproto.repo.getRecord on that key, from your account's own server.
Mastodon
How we confirm it
A1 Lane checks your server for the post and records the visibility your server actually applied.
If confirmation is missing
The receipt says Unconfirmed while A1 Lane looks, allowing your server time to update.
Technical references
Publish: POST /api/v1/statuses with an Idempotency-Key, which your server honours for about an hour. Confirm: GET /api/v1/statuses/:id, including the visibility your server applied. Lost response: a search of your recent statuses for its media IDs or the same text; the post is called absent only after a settling period.
Discord
How we confirm it
A1 Lane reads the message back from Discord.
If confirmation is missing
If Discord's confirmation is missing, the receipt says Unconfirmed. A1 Lane automatically checks five times over the next seven and a half hours. If Discord answers that the message isn't there, the receipt changes to Couldn't publish and you can retry safely. If Discord can't tell us, the receipt stays Unconfirmed and A1 Lane never re-sends by itself: check the channel, then choose 'Check Discord now' or retry from the receipt.
Technical references
Publish: Execute Webhook with wait=true, so Discord confirms the message was saved; mentions are disabled so a scheduled post never pings everyone. Confirm: Get Webhook Message through the same webhook.
Telegram
How we confirm it
Telegram only confirms the send. Telegram's Bot API has no way to read a channel post back, so the receipt records Telegram's own send response and says Delivered (limited).
If confirmation is missing
The receipt stays Unconfirmed until a workspace owner or admin retries it or marks it resolved. Check Telegram first.
Technical references
Publish: sendMessage, sendPhoto or sendVideo through your bot; a video that isn't MP4 goes as a file through sendDocument, and an album of 2–10 items as one sendMediaGroup.
Not available to connect yet
Each is waiting on its platform's review of A1 Lane's app. Their routes are described on each channel page.
- Waiting for platform approval
- TikTok
- Waiting for platform approval
- Facebook Pages
- Waiting for platform approval
- Waiting for platform approval
- Threads
- Waiting for platform approval
Written against A1 Lane on 2026-11-11.