What's the correct way to not allow free
What's the correct way to not allow free users $5 from running my actor?
Dyou can block or limit them in your Actor code.
DDetect if the user is on a free plan
Use the APIFY_USER_IS_PAYING env var (or SDK helper) in your Actor
Use the APIFY_USER_IS_PAYING env var (or SDK helper) in your Actor
Susing the sdk I get an error
S
Dimport { Actor } from 'apify';
await Actor.init();
const { userIsPaying } = Actor.getEnv(); // true = paying plan, false = free [User paying env]
if (!userIsPaying) {
// Block free users completely
throw new Error('This Actor is only available for paying Apify users.');
}
// …rest of your logic…
await Actor.exit();
await Actor.init();
const { userIsPaying } = Actor.getEnv(); // true = paying plan, false = free [User paying env]
if (!userIsPaying) {
// Block free users completely
throw new Error('This Actor is only available for paying Apify users.');
}
// …rest of your logic…
await Actor.exit();
How to migrate your Actor to limited permissions. Common migration paths, code examples, and common issues.
Sdo I need to configure the settings of the actor as full permissions or limited permissions?
SAlso is this snippet outdated?
Dinstead of blocking free users entirely, you can still allow them to run the Actor but with limits.
Syes I want to allow them to run the actor with a limited set of filters and if they are paying they can fully use all the filters
Sbut I need a proper way to detect free users
DYou can 100% do that. The proper, supported way to detect free vs paying users is to use Apify’s built-in flag:
APIFY_USER_IS_PAYING → accessible via Actor.getEnv().
APIFY_USER_IS_PAYING → accessible via Actor.getEnv().
Dconst { userIsPaying } = Actor.getEnv();
DThis works even with limited permissions and doesn’t require calling the user API.
Sgot it, nice
is userIsPaying a string or a boolean
is userIsPaying a string or a boolean
DuserIsPaying is a boolean not a string.
DYou can also create a small dummy Actor to test this before adding it to your main one.
DThat way you can confirm how userIsPaying behaves for free vs paying accounts without publishing or affecting your real product Actor. After you verify the behavior, just move the same logic into your main Actor.