#Ivy_Ray

1 messages · Page 1 of 1 (latest)

knotty sigilBOT
keen wolf
#

Can you share an example evt_xxx ID you're having issues with?

tender lagoon
#

I do not have an access to live dashboard to check event id, so I could catch that only by trying to log it, I need to change code for that

keen wolf
#

I suspect your test/live webhooks are pinned to different API versions, so conflicting with the SDK version in your integration

#

I need some kind of object ID to confirm that though

tender lagoon
#

can i get these ids programmably or using curl?

keen wolf
#

Doesn't even need to be an Event, a Payment Intent – anything. Otherwise I can't check your account logs

tender lagoon
#

it asks for host password

keen wolf
tender lagoon
#

got it

#

"evt_1MXNdNBuT55Zfo4AahHY7kVE"

keen wolf
#

So to confirm: event serialisation works in test mode, but not live?

tender lagoon
#

i mean my code works when connected todifferent test account, not test mode of this account

keen wolf
#

Got it. But yes, SDK version is likely issue: 22.1.0 is pinned to 2022-11-15 ands that account (and inherently webhook) is on 2020-08-27

tender lagoon
#

can i change that account api version to 2022-11-15 using curl?

keen wolf
#

No, you'd upgrade it via the Dashboard

tender lagoon
#

so I should ask the client to do that because they wouldnt give me the access to live acc

keen wolf
#

So you could create a new webhook endpoint with the 2022-11-15 version to confirm the issue

tender lagoon
#

in that case both webhooks will try to send events?

#

just different versions of it?

keen wolf
#

Yes, the shape of the event payloads will match that specific API version

#

Which is what that version of the SDK expects

tender lagoon
#

maybe i should update existing endpoint to eliminate double requests

#

just to add version to the link

keen wolf
#

You can't update the API version of an existing webhook

tender lagoon
#

i see

#

something like this?

keen wolf
#

But yes, should work