platform_not_enabled

​

What triggers it

• POST /v1/accounts/connect/:platform against a platform whose developer-portal review hasn’t been approved for your app.
• POST /v1/posts with a targets[].platform that points at a not-yet-enabled platform.
• An admin toggled a platform off for the org without disconnecting existing accounts (rare).

​

Response shape

{
  "error": {
    "code": "platform_not_enabled",
    "platform": "tiktok",
    "message": "tiktok is pending platform approval and not yet connectable.",
    "remediation": "Subscribe to changelog updates for launch notifications, or self-host with your own platform credentials.",
    "docUrl": "https://docs.letmepost.dev/errors/platform_not_enabled",
    "requestId": "req_..."
  }
}

​

What to do

• Check the current state first. Every platform letmepost supports is live or trial today, so the hosted API does not return this error for any of them. It fires when a platform has been put into pending deliberately — on a self-hosted instance, or during a rollback. POST /v1/accounts/connect/:platform carries a state field (live, trial, or pending); the platforms overview tracks the same thing, and the changelog announces changes.
• For self-host deployments — check that the platform’s OAuth credentials are present in your environment (e.g. META_APP_ID, TWITTER_CLIENT_ID). The platform stays disabled if its credentials are unset. You can also flip a platform live yourself with PLATFORM_STATE_OVERRIDES (e.g. PLATFORM_STATE_OVERRIDES=tiktok:live).
• For the meantime — Bluesky has no upstream review gate and works for every signup today. The API surface (POST /v1/posts) is identical, so any code you write against Bluesky carries over.

​

Related

• Platforms overview — current support status.
• Self-host environment — environment variables that gate each platform.