{"version":"2.1.227","anchor":"bad-auth-headers-reported-with-their-real-error-code","canonical_anchor":"bad-auth-headers-reported-with-their-real-error-code","heading":"Bad auth headers reported with their real error code","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/bad-auth-headers-reported-with-their-real-error-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Bad auth headers reported with their real error code\n\nBad auth header errors now show the real error code, including keys you set yourself.\n\n**What**\n\nAPI errors with code `invalid_request_header` are now logged the same way as invalid API key errors, showing the actual code rather than falling into generic handling. An API key verification failure is also now recognised when the header at fault is an `X-Api-Key` you supplied yourself rather than one coming from `ANTHROPIC_CUSTOM_HEADERS`.\n\n**Evidence**\n\n`invalid_request_header`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}