fix(openapi): align schemas with actual API responses - #2932
Merged
Conversation
vdusek
added
adhoc
Contributor
|
🗑️ Preview for this PR was deleted. |
janbuchar
approved these changes
Aug 31, 2026
vdusek
pushed a commit
to apify/apify-client-python
that referenced
this pull request
Aug 31, 2026
…d datetime usage dates (#1041) Regenerates the models from the [published OpenAPI specification](https://docs.apify.com/api/openapi.json) (`v2-2026-08-27T071624Z` -> `v2-2026-08-30T172245Z`), which now describes the API's actual behavior after apify/apify-docs#2932. User-facing changes: - `Task.input`, `CreateTaskRequest.input`, and `UpdateTaskRequest.input` also accept a list of objects, which the API stores and returns. - `DailyServiceUsages.date` is a timezone-aware `datetime` instead of `str`. - `Run.general_access` is optional - the API omits it for a run that follows the owner's account setting. - `UserPrivateInfo.plan`, `effective_platform_features`, and `is_paying` are optional - `GET /v2/users/{userId}` responses don't carry them. Previously, responses with any of these shapes failed model validation. Closes #1040 (a manual test run of the same regeneration against a pre-merge bundle of the spec). > Generated by the [Regenerate models](https://github.com/apify/apify-client-python/actions/workflows/on_schedule_regenerate_models.yaml) workflow.
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
3 participants
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.
The OpenAPI spec now describes what the API actually returns: nullable
generalAccesson storages and runs (and not required onRun), nullablereadme/input/changeloginActorDefinition, taskinputas an object or an array of objects, the private user fields optional onUserPrivateInfo, andformat: date-timeonDailyServiceUsages.date. These are the six deviations the JS client had to widen its generated zod schemas for in apify/apify-client-js#1016.✍️ Drafted by Claude Code