Conversation
Charge endpoint's idempotency-key header is now required and documented to expire 3 minutes after the charge (client already always sends it); task publish limits changed to 10/Actor and 100/account. Both are doc-only changes, plus a hermetic unit test covering the charge request shape. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014rjxmcnw3QwFHZhZyM6udx
apify-service-account
added
the
tested
apify-service-account
added
the
t-tooling
Addresses the review's two non-blocking observations: docs/tasks.md now mirrors the "contact support" clause from the publish() doc comment, and the charge unit test also asserts the request URL. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014rjxmcnw3QwFHZhZyM6udx
Pijukatel
added
the
adhoc
Claude
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
3 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.
Summary
Syncs the Rust client against the OpenAPI spec version bump from
v2-2026-09-10T091137Ztov2-2026-09-24T114302Z(apify/apify-docs#3002, apify/apify-docs#3013). No new/removedendpoints; both source PRs only changed descriptions and one
requiredflag:idempotency-keyheader is nowrequired: trueand documented toexpire 3 minutes after the charge. The client already always sends this header
(auto-generating one when omitted), so this is a documentation-only update
(
RunChargeOptions::idempotency_key,docs/runs.md).(contact support to raise). Documentation-only update (
TaskClient::publish,docs/tasks.md).Also added a hermetic unit test (
charge_sends_required_idempotency_key_header) covering thecharge request's header, URL and body shape, since a live integration test isn't feasible — the
endpoint must be called from inside the Actor run itself with that run's own token.
Bumped crate version
0.10.1->0.10.2(patch, no breaking changes) andAPI_SPEC_VERSION.Review
Reviewed via
/review-client: Approved, no open items. Verified independently against thelive OpenAPI spec (fetched directly, not from the implementer's summary); full endpoint-coverage
check found no missing in-scope endpoints; staff-review, coding-style and cheating checks clean.
Test plan
cargo buildcargo fmt --all -- --checkcargo clippy --all-targets -- -D warningscargo test --lib --tests -- --skip example_ --test-threads=4(all pass, liveAPIFY_TOKEN)cargo test --test examples --test-threads=4(8/8 pass, live)cargo test --doc --test-threads=4(35/35 pass)