Pricing model: Pay per event Start date: August 3, 2025 A block of up to 1000 successfully processed dataset rows: $0.50

For the charging call, Im using the API directly as Im not building with python or js (I may revisit this, but that is not today's project). Im using the same event name configured in the Console. I do notice a couple of issues around docs for the API call ( https://docs.apify.com/api/v2/post-charge-run ) 1) it says pay-per-event actors are alpha. I believe this is no longer true? The Monetization step in the Console pushes towards PPE anyway, do not in any way describe as not ready for full use. 2) the docs (above) mention a property called 'eventCount' but if i use this property it complains about a missing 'count' property. So i switched to using 'count' instead of 'eventCount' and when i do so, i get a 'operation is not allowed' error.

Ive looked up the 'charge' function in both the python (run.py) and js (run.ts) clients. They both do the same thing and dont do anything complicated. It looks like Im doing the same thing as them. Any updates on this? Thanks

As I am currently completely blocked by my other issue: https://discordapp.com/channels/801163717915574323/1401892779973677230/1401892779973677230 , I have not done any more digging on this one. But is there any other info I can share here on what I'm doing, to help resolve or understand what is or isnt happening here? Im not using the SDKs (using a different language), but instead calling the API directly. Ive looked at what the SDKs are doing, and it looks like Im doing the same thing. I am taking the API token from the container

APIFY_TOKEN

environment variable, and specifying it as a URL parameter e.g.

https://api.apify.com/v2/actor-runs/{runId}/charge?token={ApifyApiToken}

This has worked fine for every API call I'm making from a container (I'll change to a header once I get stuff working). I am specifying the

idempotency-key

header too. The API does seem to be accepting the payload Im sending - so I believe that is correct (as missing payload properties were returning a different error). I dont understand why the run input's

pricingInfo.pricingModel

is not

PAY_PER_EVENT

when the Console does show PPE configured (green & active). I cant see the exact event name configured through the Console (since the Console does not show it once it has been accepted), but it should be

SUCCESSFUL_PROCESSED_1000

The testing ive done that shows the run input's unexpected

pricingModel

has been both from my organisation and from my personal account. I understand that at least the latter (if not both) should really be seeing the correct input

pricingInfo

.

We throw

operationNotAllowed

when

actorRunId

is different from

runId

in the API endpoint. Can you double-check that when you call https://api.apify.com/v2/actor-runs/:runId/charge you use the correct

runId

in the API endpoint?

Should I be getting the RunId from elsewhere? Even if I did get the RunId from somewhere else (environment variable?), I'm also expecting the pricing info from that

input.payload

too, which also seems to be for the parent actor run, not for this integration run (i.e. pricing model is not for my integration actor)

I updated my actor to take the RunID from the ACTOR_RUN_ID environment variable (which is correct). Now the 'charge' API call is returning success 👍 . Next, where else can I get the pricing info, so I can get the configured "max charge per run" 🤔