#cberube

1 messages · Page 1 of 1 (latest)

river citrusBOT
quaint crest
#

The key should start with whsec_

gilded bronze
#

Fix the key already. It was hard to find.

quaint crest
#

Awesome, so is this working for you now?

gilded bronze
#

But the url doesn't contain the required scheme.

#

Still bad request

#

Will resend work. Or, do I need to crate a new customer?

quaint crest
#

resending shoudl work

gilded bronze
#

"message": "Invalid URL: An explicit scheme (such as https) must be provided.",

#

Where am I supposed to declare it?

quaint crest
#

Where exactly are you getting that error?

gilded bronze
#

Webhook logs
I just recreated another webhook for testing.

quaint crest
#

Can you send me the ID for the event that got this error?

gilded bronze
#

Yes: evt_1OmIseJ36fJ52FffV0EXjCJV
API version is wrong. How can I upgrade it to 2023-10-16.

river citrusBOT
gilded bronze
#

2023-10-16
Latest
2020-08-27
Default

rigid root
#

Hello! I'm taking over and catching up...

gilded bronze
#

I will upgrade the api first since have dons it in the client already.

#

Bad request we_1OmIqsJ36fJ52FffulK6m04a

rigid root
#

What do you mean by "bad request"? Can you provide more details?

gilded bronze
#

Customer creation works but the webhook Webhook signature verification fails. Just updated with new code example.

rigid root
#

Signature verification typically fails if you're using the wrong webhook secret or if you're not passing the raw, unaltered, unparsed body to the Event creation function.

gilded bronze
#

I did an update similar to whats was suggested
.post('/webhook', bodyParser.raw({type: 'application/json'}), (req: CustomRequest, res: Response) => {
Data is there... but still failing.

rigid root
#

You're 100% certain you're using the correct secret? Each Webhook Endpoint has a different one.

gilded bronze
#

The secret I have from the cli is different from the one in the UI.

rigid root
#

Yep, they're all different.

gilded bronze
#

Which one do i use.