You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
3.0.0: client.actor(...).get() fails with validation errors #811
{ValidationError}3 validation errors for ActorResponse
data.pricingInfos.2.PRICE_PER_DATASET_ITEM.pricePerUnitUsd
Field required [type=missin...', 'e... 'isPrimaryEvent': True}, input_type=dict]
For further information visit https://errors.pydantic.dev/2.13/v/missing
{ValidationError}1 validation error for BuildResponse
data.actorDefinition.version
String should match pattern '^[0-9]+\.[0-9]+$' [type=strin...put_value='0.0.1', input_type=str]
For further information visit https://errors.pydantic.dev/2.13/v/string_pattern_mismatch
Hi @zhemaituk, thank you for reporting this, and sorry for the inconvenience.
In this major release, we made a big step forward by adding Pydantic models for all outputs (API responses). However, it looks like there are still some discrepancies between the OpenAPI specs and the actual API behaviour. Since the models and types are generated from the OpenAPI specs, these discrepancies can, unfortunately, result in validation errors like this one.
I'm looking into it and will try to resolve them as soon as possible.
It includes fixes for the issues you reported, along with a few more. I also updated the upgrade guide so it no longer mentions internal modules, to avoid confusion about what is and isn't part of the public interface and safe to import.
Activity
zhemaituk commentedon May 21, 2026
One more:
Result:
zhemaituk commentedon May 21, 2026
Generally 3.0.0 feels undercooked. Encountered above issues in just a few minutes of usage.
A few other items:
_modelsand_literalsare marked as protected (_name), but documentation suggests it's public API (e.g. here https://docs.apify.com/api/client/python/docs/upgrading/upgrading-to-v3).Field names are inconsistent. E.g. BuildShort.buildNumber is available camelCase only, no build_number.
fix(openapi): align Actor pricing and version schemas with live API (#…
vdusek commentedon May 22, 2026
Hi @zhemaituk, thank you for reporting this, and sorry for the inconvenience.
In this major release, we made a big step forward by adding Pydantic models for all outputs (API responses). However, it looks like there are still some discrepancies between the OpenAPI specs and the actual API behaviour. Since the models and types are generated from the OpenAPI specs, these discrepancies can, unfortunately, result in validation errors like this one.
I'm looking into it and will try to resolve them as soon as possible.
fix: Add support for tiered pricing in Actor charge events (#818)
test: cover tiered pricing and multi-segment actor version in integra…
test: cover tiered pricing and multi-segment actor version in integra…
vdusek commentedon May 22, 2026
@zhemaituk, please try the new patch version: https://pypi.org/project/apify-client/3.0.1/
It includes fixes for the issues you reported, along with a few more. I also updated the upgrade guide so it no longer mentions internal modules, to avoid confusion about what is and isn't part of the public interface and safe to import.
Thank you.
zhemaituk commentedon May 22, 2026
Thank you for the quick turnaround! Works great.
fix(openapi): Add missing response fields returned by the live API (#…