You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -23,9 +23,9 @@ If you want more details about PPE pricing, please refer to our [PPE documentati
23
23
24
24
After monetization is set in the Apify console, you can add <ApiLinkto="class/Actor#charge">`Actor.charge`</ApiLink> calls to your code and start monetizing!
Then you just push your code to Apify and that's it! The SDK will even keep track of the max total charge setting for you, so you will not provide more value than what the user chose to pay for.
31
31
@@ -35,9 +35,9 @@ If you need finer control over charging, you can access call <ApiLink to="class/
35
35
36
36
When you plan to start using the pay-per-event pricing model for an Actor that is already monetized with a different pricing model, your source code will need support both pricing models during the transition period enforced by the Apify platform. Arguably the most frequent case is the transition from the pay-per-result model which utilizes the `ACTOR_MAX_PAID_DATASET_ITEMS` environment variable to prevent returning unpaid dataset items. The following is an example how to handle such scenarios. The key part is the <ApiLinkto="class/ChargingManager#get_pricing_info">`ChargingManager.get_pricing_info()`</ApiLink> method which returns information about the current pricing model.
0 commit comments