platform_auth_failed.
What triggers it
- No
Authorizationheader. - Header doesn’t start with
Bearer. - Key is unknown (typo, revoked, deleted org).
- Token doesn’t start with
lmp_live_orlmp_test_— anything else isn’t recognised as a key at all.
The prefix is not an environment check.
lmp_live_ and lmp_test_ take the same code path against the same base URL, so a test key will never be rejected for being “the wrong environment” — it just publishes. See authentication.Response shape
unauthenticated.json
Remediation
- Mint or rotate a key in the dashboard’s API keys page.
- Confirm you’re sending the whole secret, prefix included.
- Confirm the key wasn’t revoked — revocation is immediate.
Related
- Authentication — full key shape + scoping rules.
unauthorized— authenticated but not allowed.platform_auth_failed— upstream platform token issue.

