Zeref

[burnt granite]

hi! does it cause an actual issue or are you just curious?

if that is your default version than any request made without explicitly passing apiVersion will use it(so if you have any code not using that they will appear there), and there are various internal APIs our hosted pages might call that just use your default version and might inflate that stat

[torn heart]

I monitor the payments and webhooks, everything works fine but under Developer -> Logs I can see bunch of 404 errors with the message "resource_missing - payment_page
No such payment_page: SOME_KEY"

[burnt granite]

well you said apiKey: '2022-11-15'

which is wrong

[torn heart]

I can't tell what is calling that route /v1/payment_pages/cs_xxxxx
My guess is the checkout page

[burnt granite]

I assume you typo'd it when posting here on Discord but to be clear that's not correct

[torn heart]

apiVersion*

[burnt granite]

you'd use apiKey:"pk_xxxxx" (your publishable API key); api_version or apiVersion is something else

if you're getting a 'no such payment page' error it means you're using the wrong API key somewhere

do you have a link I can visit to replicate your problem like your payments page?

or can you share more context like exact code you're using and an example cs_xxxx CheckoutSession ID

[torn heart]

are these called from checkout page?

[torn heart]

I am using my api key to generate the checkout page and redirect the user to it.

[torn heart]

there is no problem, just the 404 under developer -> logs

[torn heart]

where can I share it?

[burnt granite]

in this thread

[burnt granite]

are they happening when you yourself are testing something?

[torn heart]

cs_live_a1m7TMqvLzU7WAFDIilQDKItSpkNdidD5zCD6jAsIpeFb7dTkYTw8Z5EFJ

By just visiting the checkout page, I see a new entry under Developer -> Logs
So it's the checkout page that is calling those routes with the older/default api version

[burnt granite]

I think most likely it's just someone or a bot trying to attempt payment on that specific ChecoutSession many times unsuccessfully. I'd just ignore it

[torn heart]

I expire sessions after 1 failed payment.

[burnt granite]

ah well there you go then

that's why you get a 404, you manually expired it, and then if people keep trying, they'll get that 404

[torn heart]

okay got it. I think I will upgrade the version on the dashboard as well so both checkout page and api use the same version.