Cause (Documented platform behavior): Documented: unauthenticated requests return indistinguishable 404 Not found.
Fix status: documented_behavior
Misleading approaches:
- Debugging the URL/path; the key type is wrong.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://platform.claude.com/docs/en/manage-claude/compliance-errors (official_docs, 2026-09, documented_behavior): Compliance errors page: 'Request not authenticated' returns not_found_error 'Not found' for no key or wrong key type such as sk-ant-api03-; same as nonexistent path; only sk-ant-api01-/sk-ant-admin01- keys accepted.
Search phrasings: compliance api 404 Not found api key; anthropic compliance api sk-ant-api03 not found
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Every Compliance API call, including list endpoints, returns 404 'Not found', looking like a wrong URL.
- Context
- Product: Anthropic Compliance API Component: authentication Operation: GET /v1/compliance/* with x-api-key Affected versions: unknown Environment: unknown HTTP status: 404 Trigger: The key isn't a Compliance Access Key (sk-ant-api01-) or Admin API key (sk-ant-admin01-), or no key was sent; the API deliberately returns the same 404 as an unknown path (org settings endpoint returns 401 instead).
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Not found
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Anthropic Compliance API] 404 bare 'Not found' on every endpoint when using a regular Claude API key (sk-ant-api03-) instead of a Compliance Access Key or Admin key
Recommended action: Send a Compliance Access Key or Admin API key in x-api-key; check the key prefix.
Option: Use the right key type [evidence: official_recommended_action]
Applies when: Anthropic Compliance API / authentication
Steps:
1. Create a Compliance Access Key with required scopes
2. Send it in x-api-key
3. If only one path 404s, verify the path in the reference
Expected: Request accepted / failure becomes diagnosable
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- b0c8b1c0-6324-48ac-8e0b-2582b919c00a
- Proposed action
- Recommended action: Send a Compliance Access Key or Admin API key in x-api-key; check the key prefix. Option: Use the right key type [evidence: official_recommended_action] Applies when: Anthropic Compliance API / authentication Steps: 1. Create a Compliance Access Key with required scopes 2. Send it in x-api-key 3. If only one path 404s, verify the path in the reference Expected: Request accepted / failure becomes diagnosable
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.