apify 3.3.2b5__tar.gz → 3.3.3__tar.gz

apify-3.3.2b5/.github/workflows/_release_docs.yaml → apify-3.3.3/.github/workflows/manual_release_docs.yaml

@@ -1,4 +1,4 @@
-name: Doc release
+name: Release docs
 
 on:
   # Runs when manually triggered from the GitHub UI.
@@ -8,6 +8,7 @@ on:
   workflow_call:
     inputs:
       ref:
+        description: Git ref to checkout.
         required: true
         type: string
 
@@ -17,11 +18,10 @@ permissions:
 env:
   NODE_VERSION: 22
   PYTHON_VERSION: 3.14
-  CHECKOUT_REF: ${{ github.event_name == 'workflow_call' && inputs.ref || github.ref }}
 
 jobs:
   release_docs:
-    name: Doc release
+    name: Release docs
     environment:
       name: github-pages
     permissions:
@@ -35,7 +35,7 @@ jobs:
         uses: actions/checkout@v6
         with:
           token: ${{ secrets.APIFY_SERVICE_ACCOUNT_GITHUB_TOKEN }}
-          ref: ${{ env.CHECKOUT_REF }}
+          ref: ${{ inputs.ref || github.event.repository.default_branch }}
 
       - name: Set up Node
         uses: actions/setup-node@v6
@@ -59,13 +59,13 @@ jobs:
         run: uv run poe update-docs-theme
 
       - name: Commit the updated package.json and lockfile
-        run: |
-          git config user.name 'GitHub Actions'
-          git config user.email 'github-actions[bot]@users.noreply.github.com'
-          git add website/package.json
-          git add website/yarn.lock
-          git diff-index --quiet HEAD || git commit -m 'chore: Automatic docs theme update [skip ci]' || true
-          git push
+        uses: EndBug/add-and-commit@v10
+        with:
+          add: website/package.json website/yarn.lock
+          message: "chore: Automatic docs theme update [skip ci]"
+          default_author: github_actions
+          # `actions/checkout` detaches HEAD on SHA refs; EndBug needs a branch to push.
+          new_branch: ${{ github.event.repository.default_branch }}
 
       - name: Build docs
         run: uv run poe build-docs
@@ -74,7 +74,7 @@ jobs:
           SEGMENT_TOKEN: ${{ secrets.SEGMENT_TOKEN }}
 
       - name: Set up GitHub Pages
-        uses: actions/configure-pages@v5
+        uses: actions/configure-pages@v6
 
       - name: Upload GitHub Pages artifact
         uses: actions/upload-pages-artifact@v4

{apify-3.3.2b5 → apify-3.3.3}/.github/workflows/manual_release_stable.yaml

@@ -98,75 +98,20 @@ jobs:
           version_number: ${{ needs.release_prepare.outputs.version_number }}
           ref: ${{ needs.changelog_update.outputs.changelog_commitish }}
 
-      # Publishes the package to PyPI using PyPA official GitHub action with OIDC authentication.
+      # Publish the package to PyPI using PyPA official GitHub action with OIDC authentication.
       - name: Publish package to PyPI
         uses: pypa/gh-action-pypi-publish@release/v1
 
   version_docs:
     name: Version docs
     needs: [release_prepare, changelog_update, pypi_publish]
-    runs-on: ubuntu-latest
-    outputs:
-      version_docs_commitish: ${{ steps.commit_versioned_docs.outputs.commit_long_sha }}
     permissions:
       contents: write
-    env:
-      NODE_VERSION: 22
-      PYTHON_VERSION: 3.14
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v6
-        with:
-          token: ${{ secrets.APIFY_SERVICE_ACCOUNT_GITHUB_TOKEN }}
-          ref: ${{ needs.changelog_update.outputs.changelog_commitish }}
-
-      - name: Set up Node
-        uses: actions/setup-node@v6
-        with:
-          node-version: ${{ env.NODE_VERSION }}
-
-      - name: Set up Python
-        uses: actions/setup-python@v6
-        with:
-          python-version: ${{ env.PYTHON_VERSION }}
-
-      - name: Set up uv package manager
-        uses: astral-sh/setup-uv@v7
-        with:
-          python-version: ${{ env.PYTHON_VERSION }}
-
-      - name: Install Python dependencies
-        run: uv run poe install-dev
-
-      - name: Install website dependencies
-        run: |
-          cd website
-          corepack enable
-          yarn install
-
-      - name: Snapshot the current version
-        run: |
-          cd website
-          VERSION="$(python -c "import tomllib, pathlib; print(tomllib.loads(pathlib.Path('../pyproject.toml').read_text())['project']['version'])")"
-          MAJOR_MINOR="$(echo "$VERSION" | cut -d. -f1-2)"
-          export MAJOR_MINOR
-          # Remove existing version if present (patch releases override)
-          rm -rf "versioned_docs/version-${MAJOR_MINOR}"
-          rm -rf "versioned_sidebars/version-${MAJOR_MINOR}-sidebars.json"
-          jq 'map(select(. != env.MAJOR_MINOR))' versions.json > tmp.json && mv tmp.json versions.json
-          # Build API reference and create version snapshots
-          bash build_api_reference.sh
-          npx docusaurus docs:version "$MAJOR_MINOR"
-          npx docusaurus api:version "$MAJOR_MINOR"
-
-      - name: Commit and push versioned docs
-        id: commit_versioned_docs
-        uses: EndBug/add-and-commit@v10
-        with:
-          add: "website/versioned_docs website/versioned_sidebars website/versions.json"
-          message: "docs: version ${{ needs.release_prepare.outputs.version_number }} docs [skip ci]"
-          default_author: github_actions
+    uses: ./.github/workflows/manual_version_docs.yaml
+    with:
+      # Commit the version docs changes on top of the changelog commit.
+      ref: ${{ needs.changelog_update.outputs.changelog_commitish }}
+    secrets: inherit
 
   doc_release:
     name: Doc release
@@ -175,9 +120,9 @@ jobs:
       contents: write
       pages: write
       id-token: write
-    uses: ./.github/workflows/_release_docs.yaml
+    uses: ./.github/workflows/manual_release_docs.yaml
     with:
-      # Use the version_docs commit to include both changelog and versioned docs.
+      # Commit the docs release changes on top of the version docs commit.
       ref: ${{ needs.version_docs.outputs.version_docs_commitish }}
     secrets: inherit
 

apify-3.3.3/.github/workflows/manual_version_docs.yaml

@@ -0,0 +1,119 @@
+name: Version docs
+
+on:
+  # Runs when manually triggered from the GitHub UI.
+  workflow_dispatch:
+
+  # Runs when invoked by another workflow.
+  workflow_call:
+    inputs:
+      ref:
+        description: Git ref to checkout.
+        required: true
+        type: string
+    outputs:
+      version_docs_commitish:
+        description: The commit SHA of the versioned docs commit.
+        value: ${{ jobs.version_docs.outputs.version_docs_commitish }}
+
+concurrency:
+  group: version-docs
+  cancel-in-progress: false
+
+permissions:
+  contents: read
+
+env:
+  NODE_VERSION: "22"
+  PYTHON_VERSION: "3.14"
+
+jobs:
+  version_docs:
+    name: Version docs
+    runs-on: ubuntu-latest
+    outputs:
+      version_docs_commitish: ${{ steps.resolve_commitish.outputs.commitish }}
+    permissions:
+      contents: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v6
+        with:
+          token: ${{ secrets.APIFY_SERVICE_ACCOUNT_GITHUB_TOKEN }}
+          ref: ${{ inputs.ref || github.event.repository.default_branch }}
+
+      - name: Set up Node
+        uses: actions/setup-node@v6
+        with:
+          node-version: ${{ env.NODE_VERSION }}
+
+      - name: Set up Python
+        uses: actions/setup-python@v6
+        with:
+          python-version: ${{ env.PYTHON_VERSION }}
+
+      - name: Set up uv package manager
+        uses: astral-sh/setup-uv@v7
+        with:
+          python-version: ${{ env.PYTHON_VERSION }}
+
+      - name: Install Python dependencies
+        run: uv run poe install-dev
+
+      - name: Snapshot the current version
+        id: snapshot
+        run: |
+          cd website
+          corepack enable
+          yarn install
+
+          # Extract version from pyproject.toml.
+          FULL_VERSION="$(uv version --short)"
+          MAJOR_MINOR_VERSION="$(echo "$FULL_VERSION" | cut -d. -f1-2)"
+          MAJOR_VERSION="$(echo "$FULL_VERSION" | cut -d. -f1)"
+          echo "version=$FULL_VERSION" >> "$GITHUB_OUTPUT"
+          echo "Version: $FULL_VERSION, Major.Minor: $MAJOR_MINOR_VERSION, Major: $MAJOR_VERSION"
+
+          # Find the existing versions for this major in versions.json (if any).
+          if [[ -f versions.json ]]; then
+            OLD_VERSIONS="$(jq -r --arg major "$MAJOR_VERSION" '.[] | select(startswith($major + "."))' versions.json)"
+          else
+            OLD_VERSIONS=""
+            echo "[]" > versions.json
+          fi
+
+          # Remove all old versions for this major (if found).
+          if [[ -n "$OLD_VERSIONS" ]]; then
+            while IFS= read -r OLD_VERSION; do
+              [[ -z "$OLD_VERSION" ]] && continue
+              echo "Removing old version $OLD_VERSION for major $MAJOR_VERSION"
+              rm -rf "versioned_docs/version-${OLD_VERSION}"
+              rm -f "versioned_sidebars/version-${OLD_VERSION}-sidebars.json"
+            done <<< "$OLD_VERSIONS"
+            jq --arg major "$MAJOR_VERSION" 'map(select(startswith($major + ".") | not))' versions.json > tmp.json && mv tmp.json versions.json
+          else
+            echo "No existing versions found for major $MAJOR_VERSION, nothing to remove"
+          fi
+
+          # Build API reference and create Docusaurus version snapshots.
+          bash build_api_reference.sh
+          uv run npx docusaurus docs:version "$MAJOR_MINOR_VERSION"
+          uv run npx docusaurus api:version "$MAJOR_MINOR_VERSION"
+
+      - name: Commit and push versioned docs
+        id: commit_versioned_docs
+        uses: EndBug/add-and-commit@v10
+        with:
+          add: website/versioned_docs website/versioned_sidebars website/versions.json
+          message: "docs: Version docs for v${{ steps.snapshot.outputs.version }} [skip ci]"
+          default_author: github_actions
+          # `actions/checkout` detaches HEAD on SHA refs; EndBug needs a branch to push.
+          new_branch: ${{ github.event.repository.default_branch }}
+
+      - name: Resolve output commitish
+        id: resolve_commitish
+        env:
+          COMMIT_SHA: ${{ steps.commit_versioned_docs.outputs.commit_long_sha }}
+        run: |
+          echo "commitish=${COMMIT_SHA:-$(git rev-parse HEAD)}" >> "$GITHUB_OUTPUT"

{apify-3.3.2b5 → apify-3.3.3}/.github/workflows/on_master.yaml

@@ -28,7 +28,7 @@ jobs:
       contents: write
       pages: write
       id-token: write
-    uses: ./.github/workflows/_release_docs.yaml
+    uses: ./.github/workflows/manual_release_docs.yaml
     with:
       # Use the same ref as the one that triggered the workflow.
       ref: ${{ github.ref }}
@@ -108,7 +108,7 @@ jobs:
       contents: write
       pages: write
       id-token: write
-    uses: ./.github/workflows/_release_docs.yaml
+    uses: ./.github/workflows/manual_release_docs.yaml
     with:
       # Use the ref from the changelog update to include the updated changelog.
       ref: ${{ needs.changelog_update.outputs.changelog_commitish }}

{apify-3.3.2b5 → apify-3.3.3}/.gitignore

@@ -63,6 +63,8 @@ Session.vim
 
 # Docs
 docs/changelog.md
+website/versioned_docs/*/changelog.md
+website/versioned_docs/*/pyproject.toml
 
 # Website build artifacts, node dependencies
 website/build

{apify-3.3.2b5 → apify-3.3.3}/.rules.md

@@ -51,6 +51,13 @@ uv run poe e2e-tests
 - Tests are exempt from docstring rules (`D`), assert warnings (`S101`), and private member access (`SLF001`)
 - Unused imports are allowed in `__init__.py` files (re-exports)
 - **Pre-commit hooks**: lint check + type check run automatically on commit
+- **Commits**: [Conventional Commits](https://www.conventionalcommits.org/) format. Choose the type based on *what* changed, not just *why*:
+  - `feat:` / `fix:` / `perf:` / `refactor:` / `style:` — **source code only**; these trigger a release and appear in the changelog
+  - `test:` — test additions or changes (no release triggered)
+  - `docs:` — documentation changes; also triggers a doc release on master
+  - `ci:` — CI/workflow changes
+  - `chore:` — dependency bumps, tooling, and other housekeeping
+  - `build:` — build system changes
 
 ## Architecture
 

{apify-3.3.2b5 → apify-3.3.3}/CHANGELOG.md

@@ -2,8 +2,19 @@
 
 All notable changes to this project will be documented in this file.
 
-<!-- git-cliff-unreleased-start -->
-## 3.3.2 - **not yet released**
+## [3.3.3](https://github.com/apify/apify-sdk-python/releases/tag/v3.3.3) (2026-04-21)
+
+### 🐛 Bug Fixes
+
+- Cap `_list_head` request limit at `_MAX_HEAD_ITEMS` ([#869](https://github.com/apify/apify-sdk-python/pull/869)) ([1716a2a](https://github.com/apify/apify-sdk-python/commit/1716a2aa55e86769cf9deb665c02c4ba176067d7)) by [@vdusek](https://github.com/vdusek)
+- Preserve `max_total_charge_usd=0` instead of treating it as unlimited ([#870](https://github.com/apify/apify-sdk-python/pull/870)) ([714334c](https://github.com/apify/apify-sdk-python/commit/714334c00df91bf4526de26b14ecdfea05464268)) by [@vdusek](https://github.com/vdusek)
+- Avoid InvalidStateError on mid-stream platform websocket disconnect ([#867](https://github.com/apify/apify-sdk-python/pull/867)) ([4dbbd3f](https://github.com/apify/apify-sdk-python/commit/4dbbd3f82dd45c26ca6f53d16f60b3b3e045bbc6)) by [@vdusek](https://github.com/vdusek)
+- Tolerate non-UTF-8 bodies in ApifyRequestList remote sources ([#871](https://github.com/apify/apify-sdk-python/pull/871)) ([737b0dd](https://github.com/apify/apify-sdk-python/commit/737b0ddbfdd3277a01fa24c3215ddf4572bf1121)) by [@vdusek](https://github.com/vdusek)
+- Use load sentinel and injected config in AliasResolver ([#874](https://github.com/apify/apify-sdk-python/pull/874)) ([2d129ad](https://github.com/apify/apify-sdk-python/commit/2d129adafe1005fb987bf19614fc22009cb39140)) by [@vdusek](https://github.com/vdusek)
+- Honor `event_listeners_timeout` in `Actor.reboot` ([#872](https://github.com/apify/apify-sdk-python/pull/872)) ([03e73d3](https://github.com/apify/apify-sdk-python/commit/03e73d3885030d63795063a4d1acd8abad11cd19)) by [@vdusek](https://github.com/vdusek)
+
+
+## [3.3.2](https://github.com/apify/apify-sdk-python/releases/tag/v3.3.2) (2026-03-27)
 
 ### 🐛 Bug Fixes
 
@@ -14,7 +25,6 @@ All notable changes to this project will be documented in this file.
 - Handle exceptions in pre-reboot event listeners via `return_exceptions` ([#843](https://github.com/apify/apify-sdk-python/pull/843)) ([ed13597](https://github.com/apify/apify-sdk-python/commit/ed13597d7ce0d1f0c5ff5cd0d6796c96555a55ae)) by [@vdusek](https://github.com/vdusek)
 
 
-<!-- git-cliff-unreleased-end -->
 ## [3.3.1](https://github.com/apify/apify-sdk-python/releases/tag/v3.3.1) (2026-03-11)
 
 ### 🐛 Bug Fixes

{apify-3.3.2b5 → apify-3.3.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: apify
-Version: 3.3.2b5
+Version: 3.3.3
 Summary: Apify SDK for Python
 Project-URL: Apify Homepage, https://apify.com
 Project-URL: Changelog, https://docs.apify.com/sdk/python/docs/changelog
@@ -321,7 +321,7 @@ async def main() -> None:
 
             # Extract the desired data.
             data = {
-                'url': actor_input['url'],
+                'url': request.url,
                 'title': soup.title.string,
                 'h1s': [h1.text for h1 in soup.find_all('h1')],
                 'h2s': [h2.text for h2 in soup.find_all('h2')],
@@ -409,10 +409,11 @@ To create and run Python Actors locally, check the documentation for
 
 To see how you can use the Apify SDK with other popular libraries used for web scraping,
 check out our guides for using
-[Requests and HTTPX](https://docs.apify.com/sdk/python/docs/guides/requests-and-httpx),
-[Beautiful Soup](https://docs.apify.com/sdk/python/docs/guides/beautiful-soup),
+[BeautifulSoup with HTTPX](https://docs.apify.com/sdk/python/docs/guides/beautifulsoup-httpx),
+[Parsel with Impit](https://docs.apify.com/sdk/python/docs/guides/parsel-impit),
 [Playwright](https://docs.apify.com/sdk/python/docs/guides/playwright),
 [Selenium](https://docs.apify.com/sdk/python/docs/guides/selenium),
+[Crawlee](https://docs.apify.com/sdk/python/docs/guides/crawlee),
 or [Scrapy](https://docs.apify.com/sdk/python/docs/guides/scrapy).
 
 ## Usage concepts

{apify-3.3.2b5 → apify-3.3.3}/README.md

@@ -77,7 +77,7 @@ async def main() -> None:
 
             # Extract the desired data.
             data = {
-                'url': actor_input['url'],
+                'url': request.url,
                 'title': soup.title.string,
                 'h1s': [h1.text for h1 in soup.find_all('h1')],
                 'h2s': [h2.text for h2 in soup.find_all('h2')],
@@ -165,10 +165,11 @@ To create and run Python Actors locally, check the documentation for
 
 To see how you can use the Apify SDK with other popular libraries used for web scraping,
 check out our guides for using
-[Requests and HTTPX](https://docs.apify.com/sdk/python/docs/guides/requests-and-httpx),
-[Beautiful Soup](https://docs.apify.com/sdk/python/docs/guides/beautiful-soup),
+[BeautifulSoup with HTTPX](https://docs.apify.com/sdk/python/docs/guides/beautifulsoup-httpx),
+[Parsel with Impit](https://docs.apify.com/sdk/python/docs/guides/parsel-impit),
 [Playwright](https://docs.apify.com/sdk/python/docs/guides/playwright),
 [Selenium](https://docs.apify.com/sdk/python/docs/guides/selenium),
+[Crawlee](https://docs.apify.com/sdk/python/docs/guides/crawlee),
 or [Scrapy](https://docs.apify.com/sdk/python/docs/guides/scrapy).
 
 ## Usage concepts

{apify-3.3.2b5/website/versioned_docs/version-3.3 → apify-3.3.3/docs}/01_introduction/index.mdx

@@ -1,25 +1,19 @@
 ---
 id: introduction
 title: Overview
-sidebar_label: Overview
 slug: /overview
-description: 'The official library for creating Apify Actors in Python, providing tools for web scraping, automation, and data storage integration.'
+description: The official library for creating Apify Actors in Python, providing tools for web scraping, automation, and data storage integration.
 ---
 
+import CodeBlock from '@theme/CodeBlock';
+
+import IntroductionExample from '!!raw-loader!./code/01_introduction.py';
+
 The Apify SDK for Python is the official library for creating [Apify Actors](https://docs.apify.com/platform/actors) in Python. It provides useful features like Actor lifecycle management, local storage emulation, and Actor event handling.
 
-```python
-from apify import Actor
-from bs4 import BeautifulSoup
-import requests
-
-async def main():
-    async with Actor:
-        input = await Actor.get_input()
-        response = requests.get(input['url'])
-        soup = BeautifulSoup(response.content, 'html.parser')
-        await Actor.push_data({ 'url': input['url'], 'title': soup.title.string })
-```
+<CodeBlock className="language-python">
+    {IntroductionExample}
+</CodeBlock>
 
 ## What are Actors
 

{apify-3.3.2b5/website/versioned_docs/version-3.3 → apify-3.3.3/docs}/01_introduction/quick-start.mdx

@@ -1,8 +1,7 @@
 ---
 id: quick-start
 title: Quick start
-sidebar_label: Quick start
-description: 'Get started with the Apify SDK for Python by creating your first Actor and learning the basics.'
+description: Get started with the Apify SDK for Python by creating your first Actor and learning the basics.
 ---
 
 Learn how to create and run Actors using the Apify SDK for Python.
@@ -13,6 +12,9 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import CodeBlock from '@theme/CodeBlock';
 
+import MainExample from '!!raw-loader!./code/actor_structure/main.py';
+import UnderscoreMainExample from '!!raw-loader!./code/actor_structure/__main__.py';
+
 ## Step 1: Create Actors
 
 To create and run Actors in Apify Console, refer to the [Console documentation](/platform/actors/development/quick-start/web-ide).
@@ -61,33 +63,14 @@ The Actor's source code is in the `src` folder. This folder contains two importa
 
 <Tabs>
     <TabItem value="main.py" label="main.py" default>
-        <CodeBlock language="python">{
-`from apify import Actor
-${''}
-async def main():
-    async with Actor:
-        Actor.log.info('Actor input:', await Actor.get_input())
-        await Actor.set_value('OUTPUT', 'Hello, world!')`
-        }</CodeBlock>
+        <CodeBlock className="language-python">
+            {MainExample}
+        </CodeBlock>
     </TabItem>
     <TabItem value="__main__.py" label="__main.py__">
-        <CodeBlock language="python">{
-`import asyncio
-import logging
-${''}
-from apify.log import ActorLogFormatter
-${''}
-from .main import main
-${''}
-handler = logging.StreamHandler()
-handler.setFormatter(ActorLogFormatter())
-${''}
-apify_logger = logging.getLogger('apify')
-apify_logger.setLevel(logging.DEBUG)
-apify_logger.addHandler(handler)
-${''}
-asyncio.run(main())`
-        }</CodeBlock>
+        <CodeBlock className="language-python">
+            {UnderscoreMainExample}
+        </CodeBlock>
     </TabItem>
 </Tabs>
 
@@ -96,21 +79,30 @@ We recommend keeping the entrypoint for the Actor in the `src/__main__.py` file.
 
 ## Next steps
 
+### Concepts
+
+To learn more about the features of the Apify SDK and how to use them, check out the Concepts section in the sidebar:
+
+- [Actor lifecycle](../concepts/actor-lifecycle)
+- [Actor input](../concepts/actor-input)
+- [Working with storages](../concepts/storages)
+- [Actor events & state persistence](../concepts/actor-events)
+- [Proxy management](../concepts/proxy-management)
+- [Interacting with other Actors](../concepts/interacting-with-other-actors)
+- [Creating webhooks](../concepts/webhooks)
+- [Accessing Apify API](../concepts/access-apify-api)
+- [Logging](../concepts/logging)
+- [Actor configuration](../concepts/actor-configuration)
+- [Pay-per-event monetization](../concepts/pay-per-event)
+
 ### Guides
 
-To see how you can integrate the Apify SDK with some of the most popular web scraping libraries, check out our guides for working with:
+To see how you can integrate the Apify SDK with popular web scraping libraries, check out our guides:
 
-- [Requests or HTTPX](../guides/requests-and-httpx)
-- [Beautiful Soup](../guides/beautiful-soup)
+- [BeautifulSoup with HTTPX](../guides/beautifulsoup-httpx)
+- [Parsel with Impit](../guides/parsel-impit)
 - [Playwright](../guides/playwright)
 - [Selenium](../guides/selenium)
+- [Crawlee](../guides/crawlee)
 - [Scrapy](../guides/scrapy)
-
-### Usage concepts
-
-To learn more about the features of the Apify SDK and how to use them, check out the Usage Concepts section in the sidebar, especially the guides for:
-
-- [Actor lifecycle](../concepts/actor-lifecycle)
-- [Working with storages](../concepts/storages)
-- [Handling Actor events](../concepts/actor-events)
-- [How to use proxies](../concepts/proxy-management)
+- [Running webserver](../guides/running-webserver)

{apify-3.3.2b5 → apify-3.3.3}/docs/02_concepts/01_actor_lifecycle.mdx

@@ -1,6 +1,7 @@
 ---
 id: actor-lifecycle
 title: Actor lifecycle
+description: How an Apify Actor starts, runs, and shuts down, including context manager and manual control patterns.
 ---
 
 import RunnableCodeBlock from '@site/src/components/RunnableCodeBlock';
@@ -42,7 +43,15 @@ When the Actor exits, either normally or due to an exception, the SDK performs a
     </TabItem>
 </Tabs>
 
-You can also create an [`Actor`](https://docs.apify.com/sdk/python/reference/class/Actor) instance directly. This does not change its capabilities but allows you to specify optional parameters during initialization, such as disabling automatic `sys.exit()` calls or customizing timeouts. The choice between using a context manager or manual initialization depends on how much control you require over the Actor's startup and shutdown sequence.
+You can also create an [`Actor`](https://docs.apify.com/sdk/python/reference/class/Actor) instance directly. This does not change its capabilities but allows you to specify optional parameters during initialization. The key parameters are:
+
+- `configuration` — a custom [`Configuration`](https://docs.apify.com/sdk/python/reference/class/Configuration) instance to control storage paths, API URLs, and other settings.
+- `configure_logging` — whether to set up default logging configuration (default `True`). Set to `False` if you configure logging yourself.
+- `exit_process` — whether the Actor calls `sys.exit()` when the context manager exits. Defaults to `True`, except in IPython, Pytest, and Scrapy environments.
+- `event_listeners_timeout` — maximum time to wait for Actor event listeners to complete before exiting.
+- `cleanup_timeout` — maximum time to wait for cleanup tasks to finish (default 30 seconds).
+
+The choice between using a context manager or manual initialization depends on how much control you require over the Actor's startup and shutdown sequence.
 
 <Tabs groupId="request_queue">
     <TabItem value="actor_instance_with_context_manager" label="Actor instance with context manager" default>
@@ -88,12 +97,10 @@ Before triggering a reboot, persist any essential state externally (e.g., to the
 
 ## Status message
 
-[Status messages](https://docs.apify.com/platform/actors/development/programming-interface/status-messages) are lightweight, human-readable progress indicators displayed with the Actor run on the Apify platform (separate from logs). Use them to communicate high-level phases or milestones, such as "Fetching list", "Processed 120/500 pages", or "Uploading results".
+[Status messages](https://docs.apify.com/platform/actors/development/programming-interface/status-messages) are lightweight, human-readable progress indicators displayed with the Actor run in Apify Console. Use them to communicate high-level phases or milestones, such as "Fetching list", "Processed 120/500 pages", or "Uploading results". When running locally, the SDK logs the status message instead of sending it to the platform.
 
 Update the status only when the user's understanding of progress changes - avoid frequent updates for every processed item. Detailed information should go to logs or storages (dataset, key-value store) instead.
 
-The SDK optimizes updates by sending an API request only when the message text changes, so repeating the same message incurs no additional cost.
-
 <RunnableCodeBlock className="language-python" language="python">{StatusMessageExample}</RunnableCodeBlock>
 
 ## Conclusion

apify-3.3.3/docs/02_concepts/02_actor_input.mdx

@@ -0,0 +1,37 @@
+---
+id: actor-input
+title: Actor input
+description: Read and validate input data passed to your Actor at runtime.
+---
+
+import RunnableCodeBlock from '@site/src/components/RunnableCodeBlock';
+
+import InputExample from '!!raw-loader!roa-loader!./code/02_input.py';
+import RequestListExample from '!!raw-loader!roa-loader!./code/02_request_list.py';
+import ApiLink from '@site/src/components/ApiLink';
+
+The Actor gets its [input](https://docs.apify.com/platform/actors/running/input) from the input record in its default [key-value store](https://docs.apify.com/platform/storage/key-value-store).
+
+To access it, instead of reading the record manually, you can use the <ApiLink to="class/Actor#get_input">`Actor.get_input`</ApiLink> convenience method. It will get the input record key from the Actor configuration, read the record from the default key-value store,and decrypt any [secret input fields](https://docs.apify.com/platform/actors/development/secret-input).
+
+For example, if an Actor received a JSON input with two fields, `{ "firstNumber": 1, "secondNumber": 2 }`, this is how you might process it:
+
+<RunnableCodeBlock className="language-python" language="python">
+    {InputExample}
+</RunnableCodeBlock>
+
+## Loading URLs from Actor input
+
+Actors commonly receive a list of URLs to process via their input. The <ApiLink to="class/ApifyRequestList">`ApifyRequestList`</ApiLink> class (from `apify.request_loaders`) can parse the standard Apify input format for URL sources. It supports both direct URL objects (`{"url": "https://example.com"}`) and remote URL lists (`{"requestsFromUrl": "https://example.com/urls.txt"}`), where the remote file contains one URL per line.
+
+<RunnableCodeBlock className="language-python" language="python">
+    {RequestListExample}
+</RunnableCodeBlock>
+
+## Secret input fields
+
+The Apify platform supports [secret input fields](https://docs.apify.com/platform/actors/development/secret-input) that are encrypted before being stored. When you mark an input field as `"isSecret": true` in your Actor's [input schema](https://docs.apify.com/platform/actors/development/input-schema), the platform encrypts the value with the Actor's public key.
+
+No special handling is needed in your code — when you call <ApiLink to="class/Actor#get_input">`Actor.get_input`</ApiLink>, encrypted fields are automatically decrypted using the Actor's private key, which is provided by the platform via environment variables. You receive the plaintext values directly.
+
+For more details on Actor input and how to define input schemas, see the [Actor input](https://docs.apify.com/platform/actors/running/input) and [input schema](https://docs.apify.com/platform/actors/development/input-schema) documentation on the Apify platform.