#Thomas B-api-version

1 messages ยท Page 1 of 1 (latest)

bright badger
#

Hi there ๐Ÿ‘‹ what version of the API are you currently on?

coarse steppe
#

๐Ÿ™‚

#

In test mode at least

#

2020-03-02 in live.

#

Want both to be on the latest 2020-08-27. ๐Ÿ™‚

bright badger
#

Hm, let me look into this a bit further

coarse steppe
#

Awesome, thank you. I will have to go AFK for a ~1 hour in 5 minutes or so. Any quick information you could think of needing?

#

Otherwise, I'll just wait for you to get back. ๐Ÿ™‚

bright badger
#

Honestly, this is the first I'm hearing of an option to upgrade an endpoint. Usually we recommend creating a new endpoint on the updated version and then doing a cutover from one endpoint to the other. I'm a bit wary that the Upgrade Version button is referring to upgrading the accounts API version, not the webhooks.

coarse steppe
#

So what you are telling me, is that I should just create a whole new identical endpoint, and then just update my keys on my backend, done?

bright badger
#

If you're just testing, yeah that would be fine. I would not suggest this approach for live webhooks unless you've already tested and are confident your code can handle the changes.

Also keep in mind that until you disable the original webhook you will be sent duplicates of the events. They'll fail during signature verification since your code won't have the right secret for the webhook though.

coarse steppe
#

I will do it in Test mode first yes. If everything works after testing, I will just do the same in Live mode I guess. Seems to be the latest version when creating a new one, so I'll just have to to a quick switch on live when all code is tested. ๐Ÿ™‚

That'll be the approach I try, thank you. ๐Ÿ™‚