feat: expose HTTP response headers on non-streaming responses#178
Draft
bborn wants to merge 1 commit intoanthropics:mainfrom
Draft
feat: expose HTTP response headers on non-streaming responses#178bborn wants to merge 1 commit intoanthropics:mainfrom
bborn wants to merge 1 commit intoanthropics:mainfrom
Conversation
Add `_status` and `_headers` accessors to BaseModel so that non-streaming API responses expose the HTTP status code and headers (rate limits, request IDs, etc.) — matching the existing pattern on streaming responses. Closes anthropics#110 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #110
_statusand_headersaccessors toBaseModel, making HTTP response metadata available on non-streaming API responsesbase_client.rbto set these accessors after coercing the response modelrespond_to?guard so non-BaseModel return types are unaffectedThis mirrors the existing pattern on streaming responses (which already expose
.statusand.headersviaBaseStream).Usage
Test plan
test/anthropic/resources/messages/response_headers_test.rbwith tests for header and status access on non-streaming responses🤖 Generated with Claude Code