Repository navigation
Require prompt and response_format in extract(), release 0.7.0 - #8
Merged
Merged
Conversation
The API never accepted /extract without them; it now rejects such a request with 422 and an errors array. Type response_format as ExtractResponseFormat, sync the OpenAPI snapshot, and document extract in the README. Co-Authored-By: Claude Opus 5.5 <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.
Why
POST /extracthas always requiredpromptandresponse_format({"type": "json_schema", "json_schema": ...}), but the SDK made both optional and the API docs' own Python sample leftresponse_formatout, so copying it failed with 400. Gateway change: fatwang2/search1api#535 — the API now rejects these requests at the gateway with422and anerrorsarray.Changes
extract()onSearch1APIandAsyncSearch1API:promptandresponse_formatare required keyword arguments;response_formatis the newExtractResponseFormatTypedDict insearch1api.types.TARGET_BAD_REQUESTinfailureCategory).422raisesUnprocessableEntityError.Testing
pip is not available on the machine this was written on, so ruff / mypy / pytest run in CI only (3.9 and 3.12). Local check:
python -m py_compileon the changed files.Release (tag
v0.7.0) after fatwang2/search1api#535 is merged.🤖 Generated with Claude Code