Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.letmepost.dev/llms.txt

Use this file to discover all available pages before exploring further.

The credentials we hold for the connected upstream account are no longer accepted by the platform. This is distinct from unauthenticated, which is about your letmepost API key — platform_auth_failed is about the OAuth token (or app password) for the connected platform account.

​
What triggers it

  • The user revoked your app’s access from the platform’s settings page.
  • A LinkedIn token aged past its 60-day lifetime and the user hasn’t re-authenticated.
  • A Bluesky app password was deleted from bsky.app/settings/app-passwords.
  • A Threads token was rotated faster than our refresh schedule (rare, but the upstream allows it).
  • Facebook user removed your business asset from their account.

​
Response shape

platform_auth_failed.json
{
  "error": {
    "code": "platform_auth_failed",
    "message": "Bluesky rejected the session token.",
    "platform": "bluesky",
    "platformVersion": "atproto-2026-04",
    "platformResponse": { "error": "AuthMissing", "message": "..." },
    "remediation": "Reconnect the Bluesky account.",
    "requestId": "req_..."
  }
}

​
How to handle

  1. Mark the connected account as needing re-auth in your UI.
  2. Send the user through the connect flow again — see accounts.
  3. Subscribe to token.expiring and token.revoked so this doesn’t surprise you mid-publish.
The connected platform_account row stays in place; reconnecting upserts new tokens onto the same row, so post history and idempotency keys are preserved.