fix(openapi): align Actor pricing and version schemas with live API#2555
Merged
Conversation
Pydantic models generated from the spec reject real responses from
`GET /v2/acts/{id}` and `GET /v2/acts/{id}/builds/default` because the
schemas don't model tiered pricing and use an overly strict version
pattern. Make `pricePerUnitUsd` / `eventPriceUsd` optional, add
`tieredPricing` / `eventTieredPricingUsd` (plus `isPrimaryEvent` and
`isOneTimeEvent`), add common pricing-info flags returned by the API,
and relax the actor `version` pattern to accept multi-segment values
like `0.0.1`. Fixes apify/apify-client-python#811.
vdusek
added
adhoc
Contributor
|
🗑️ Preview for this PR was deleted. |
Contributor
|
Python client model regeneration failed. See workflow run. |
janbuchar
approved these changes
May 21, 2026
fnesveda
requested changes
May 21, 2026
Member
fnesveda
left a comment
fnesveda
left a comment
There was a problem hiding this comment.
Looks good, except the Actor version number changes, those are not correct. The three-number strings are build numbers, never versions.
fnesveda
approved these changes
May 22, 2026
Contributor
|
Important Action required — @vdusek please coordinate this docs PR with the Python API client PR linked below. Because this PR modifies the OpenAPI specification, the generated models in A companion PR has been opened in
|
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
4 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 Pydantic models generated from this spec in
apify-client-pythonreject real responses fromGET /v2/acts/{id}andGET /v2/acts/{id}/builds/default(see apify/apify-client-python#811). Three schema mismatches with the live API:PricePerDatasetItemActorPricingInforequiredpricePerUnitUsd, but Actors using tiered PPR pricing returntieredPricinginstead.ActorChargeEventrequiredeventPriceUsd, but tiered PPE events returneventTieredPricingUsd. The fieldsisPrimaryEventandisOneTimeEventwere also missing.ActorDefinition.versionpattern^[0-9]+\.[0-9]+$rejected semver-style triplets like0.0.1that real actors return.