Skip to content

Introduce fully typed Python API client #481

Closed

Description

@vdusek

Currently, the apify-client-python relies mostly on untyped dict and poor typing in general.

Let's introduce full type coverage across the client by defining Pydantic models for API responses and adding proper type annotations for all functions, methods, and their arguments.

Where possible, these models and types should be generated directly from the OpenAPI specification to ensure consistency with the API.

OpenAPI specs - https://docs.apify.com/api/openapi.json

Some existing solutions to explore & test:

For additional context, see parent (epic) issue - https://github.com/apify/apify-core/issues/25186.

Activity

  1. self-assigned this
    on Aug 20, 2025
  2. added
    enhancementNew feature or request.
    t-toolingIssues with this label are in the ownership of the tooling team.
    product roadmapIssues synchronized to product roadmap.
    EpicAn epic is a large body of work that can be broken down into a number of smaller issues.
    on Aug 20, 2025
  3. shubhamos-ai commented on Aug 29, 2025

    @shubhamos-ai

    This looks like a valuable enhancement! The proposed approach seems solid. I'm available to help with coding or testing if needed.

  4. removed
    EpicAn epic is a large body of work that can be broken down into a number of smaller issues.
    on Dec 10, 2025
  5. changed the title [-]Introduce fully typed client[/-] [+]Introduce fully typed Py client[/+] on Jan 15, 2026
  6. changed the title [-]Introduce fully typed Py client[/-] [+]Introduce fully typed Python API client[/+] on Feb 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request.t-toolingIssues with this label are in the ownership of the tooling team.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions