{"version":"2.1.228","anchor":"cloud-client-registry-and-error-responses-with-headers","canonical_anchor":"cloud-client-registry-and-error-responses-with-headers","heading":"Cloud client registry and error responses with headers","tier":"internal","area":"API Client","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/cloud-client-registry-and-error-responses-with-headers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Cloud client registry and error responses with headers\n\nBedrock and Vertex clients register themselves, and local server errors can now carry response headers.\n\n**What**\n\nBedrock and Vertex clients now add themselves to a module-level set when constructed, and the local server's JSON error helper accepts optional response headers so an error can carry things like an auth challenge.\n\n**Evidence**\n\n`request_id`\n\n- Area: API Client\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}