Skip to content

Add support for the request_id param in Actor.charge() #1193

Description

@patrikbraborec

Problem

Multi-tenant Server Actors serve many callers from one run. To charge the caller, the Actor has to send a raw HTTP request to /charge with the X-Apify-Request-ID header, which bypasses the SDK's charging bookkeeping.

What we want

An optional request_id param in Actor.charge() that maps the charge to the caller's account. Parity with apify/apify-sdk-js#776.

Requirements

P0

  • Actor.charge(event_name, count, request_id=...) sends X-Apify-Request-ID to /charge.
  • Calls without request_id behave as today.
  • Document request_id on the Pay per event concept page, with a multi-tenant Server Actor example.

Out of scope

  • maxChargeUsd for Standby runs. It can come later as another header and another Actor.charge() param.

Links

Nice-to-have by November 16, 2026 (Server Actors launch), must-have by end of Q4.

Activity

  1. added
    t-toolingIssues with this label are in the ownership of the tooling team.
    on Oct 16, 2026
  2. self-assigned this
    on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

t-toolingIssues with this label are in the ownership of the tooling team.

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions