Okapi Okapi

/v2/acts/* → endpoint removal

Apify API

Deprecated, no date

The /v2/acts/* endpoints are deprecated without a shutdown date, though they remain fully functional. Any future removal will cause calls targeting this path prefix to fail.


Calls it hits

  • /v2/acts/*

What to use instead of these calls

Call the same endpoints under the canonical /v2/actors/ prefix, such as /v2/actors/{actorId}/....

In Apify API's words

The /v2/acts/ prefix is deprecated but still fully functional

Apify API, Announcement

Facts

API
Apify API api.apify.com
Kind
Endpoint removal
Takes effect
No date given yet
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Apify API's own pages

Questions

When does this change take effect?

Apify API deprecated /v2/acts/* without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: Apify API has not given a shutdown date yet.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.


More from Apify API 6

  1. No date GET /v2/actors/{}/builds/{}Endpoint removal Deprecated, no date
  2. No date GET /v2/actors/{}/runs/{}Endpoint removal Deprecated, no date
  3. No date GET /v2/acts/{}/builds/{}Endpoint removal Deprecated, no date
  4. No date GET /v2/acts/{}/runs/{}Endpoint removal Deprecated, no date
  5. No date POST /v2/actors/{}/builds/{}/abortEndpoint removal Deprecated, no date
  6. No date POST /v2/actors/{}/runs/{}/abortEndpoint removal Deprecated, no date

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix.

Add to GitHub