Skip to content

docs: replace legacy /v2/acts routes with canonical /v2/actors paths - #2832

Open
marekh19 wants to merge 5 commits into
masterfrom
docs/replace-legacy-acts-routes
Open

docs: replace legacy /v2/acts routes with canonical /v2/actors paths#2832
marekh19 wants to merge 5 commits into
masterfrom
docs/replace-legacy-acts-routes

Conversation

@marekh19

@marekh19 marekh19 commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Relates to #2804

Replace legacy /v2/acts with canonical /v2/actors across docs. The paths were already canonical in the OpenAPI spec (0 /v2/acts keys), so this is prose-only drift.

  • Agent onboarding quick-reference table: 3 endpoint cells
  • GitHub integration build-trigger URL
  • PHP tutorial: 4 client calls; API tutorial: stale operation anchor + prose
  • CONTRIBUTING.md + api-doc skill reference: operationId convention documented act_runs_post. Corrected, plus a note on why an Actor's own /runs keeps the plural actors_ prefix - singular actor_runs_get would collide with the account-wide /actor-runs family.

No OpenAPI changes. operationIds are untouched, so no doc URLs move and no redirects are needed.

Console's API endpoints modal already emits /v2/actors/ (migrated in apify-core#27780), so github.md matches the UI.


  • Web counterpart: apify/apify-web#6390

Agent-facing docs taught /v2/acts, absent from the public OpenAPI
contract. Also fix the operationId convention docs, which documented
act_runs_post and would re-seed the drift on the next endpoint.
@marekh19 marekh19 added the t-web Issues with this label are in the ownership of the web team. label Jul 29, 2026
@marekh19 marekh19 self-assigned this Jul 29, 2026
@github-actions github-actions Bot added this to the 146th sprint - Web team milestone Jul 29, 2026
@apify-service-account

apify-service-account commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

✅ Preview for this PR (commit 8290b0b1) is ready at https://pr-2832.preview.docs.apify.com (see action run).

@apify-service-account

This comment was marked as outdated.

@marekh19
marekh19 marked this pull request as ready for review July 29, 2026 13:43
@marekh19
marekh19 requested a review from a team July 29, 2026 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-web Issues with this label are in the ownership of the web team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants