jericho_api | Stripe Developers | Page 1

trim sonnetBOT Jun 11, 2024, 11:09 PM

#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1250225447329861774

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

queen snow Jun 11, 2024, 11:09 PM

#

Hi there!

#

Restricted API keys shouldn't impact webhooks

#

Do you have a webhook endpoint ID (we_...) or a PaymentIntent ID I can review?

#

I can use this to pull up event delivery logs

rugged reef Jun 11, 2024, 11:11 PM

#

I listed one of the failed endpoint urls in the above text

queen snow Jun 11, 2024, 11:11 PM

#

I'll need the endpoint ID that uses this URL

#

since multiple endpoints can be configured with the same URL. it should look like we_...

rugged reef Jun 11, 2024, 11:13 PM

#

Where is that located in the Dashboard?

#

ID
req_QobBLlDu9SgMxJ

queen snow Jun 11, 2024, 11:13 PM

#

This should be sufficient! looking

rugged reef Jun 11, 2024, 11:13 PM

#

I'm seeing this ID for a failed endpoint

queen snow Jun 11, 2024, 11:14 PM

#

Just so we're on the same page, this is a request ID for a failed payment confirmation

rugged reef Jun 11, 2024, 11:14 PM

#

It would seem so

queen snow Jun 11, 2024, 11:15 PM

#

I see you have two live mode webhooks listening for payment_intent.succeeded events, and both use make.com URLs, albeit slightly different

#

You can see these in the Dashboard under Developers > Webhooks

#

I'm taking a look at the endpoint that uses the URL you shared above

rugged reef Jun 11, 2024, 11:16 PM

#

Yes - I noticed the same, though in Make we're only using the R-API

queen snow Jun 11, 2024, 11:17 PM

#

Are you able to see this? https://dashboard.stripe.com/events/evt_3PQdZ4LJNbBPKdFl01udLeFy
This is one of the payment_intent.succeeded events that failed to be delivered to the endpoint above

#

Note that the event was successfully delivered to the other make.com endpoint

#

So what we can tell from the failure is that we attempted to make a POST request to the make.com URL but that endpoint replied with a 400 and the message "There is no scenario listening for this webhook."

rugged reef Jun 11, 2024, 11:18 PM

#

So the error messages are coming from the old API key connection?

queen snow Jun 11, 2024, 11:19 PM

#

What I can see is that we attempted to make a POST request to https://hook.us1.make.com/rwi5s0osvqx2v8w1kyx1tl6z5kqcztp8 and this endpoint replied with a 400 and the message "There is no scenario listening for this webhook."

#

You probably want to reach out to Make about this if your team doesn't own/manage the webhook handler code directly

#

At least from what I can tell, we sent this particular event to two make.com URLs and only the one above failed to receive it

#

You can see both under "Webhook attempts": https://dashboard.stripe.com/events/evt_3PQdZ4LJNbBPKdFl01udLeFy

rugged reef Jun 11, 2024, 11:21 PM

#

Would using the R-API send the same event to both webhooks?

queen snow Jun 11, 2024, 11:22 PM

#

No

rugged reef Jun 11, 2024, 11:22 PM

#

I would think it would only communicate with the one. Stripe initiated the sequence, and Make responds to the JSON sent by Stripe ...

queen snow Jun 11, 2024, 11:23 PM

#

Restricted API keys are separate

#

From what I can tell, a restricted API key was used to create one of the endpoints a few days ago: https://dashboard.stripe.com/logs/req_Ydc12pV0zukpDO

rugged reef Jun 11, 2024, 11:24 PM

#

Yeah, Make gave us two days to stop using the deprecated API Keys setup.

queen snow Jun 11, 2024, 11:24 PM

#

Note the webhook endpoint URL here. This means that Make used a restricted API key to create an endpoint that listens for payment_intent.succeeded and this endpoint is successfully receiving these events at the moment. It's the make.com URL that ends in 6w22

rugged reef Jun 11, 2024, 11:25 PM

#

Perhaps they're not prepared on their end - I should check with them.

#

That brings me some peace, knowing the R-API key is responding correctly, but I can't figure out why the old key is still firing - it was removed from Make.

queen snow Jun 11, 2024, 11:26 PM

#

It really depends on how Make designed this.

rugged reef Jun 11, 2024, 11:27 PM

#

Would removing the old keys from the Stripe account work (I thought I had deleted all the old Key connections). I didn't notice the two Webhooks on the Dash.

queen snow Jun 11, 2024, 11:27 PM

#

I'm assuming that removing it from Make should also trigger some code on their end to delete a webhook endpoint: https://docs.stripe.com/api/webhook_endpoints/delete

Only their team would know about this though

#

What do you mean exactly by removing old keys?

rugged reef Jun 11, 2024, 11:28 PM

#

The Make scenarios only allow for one key, and they've all been replaced with the R APIs.

#

I would think the old keys wouldn't receive any action - I'll get a hold of Make.

queen snow Jun 11, 2024, 11:29 PM

#

I recommend working with Make, yep.

rugged reef Jun 11, 2024, 11:29 PM

#

Excellent - thank you for your help!

queen snow Jun 11, 2024, 11:30 PM

#

In case it helps, activated Stripe accounts have four keys by default (a secret and publishable key pair for test mode and live mode), and you can create additional restricted API keys

#

Creating a restricted API key in live mode doesn't replace your live mode secret key

rugged reef Jun 11, 2024, 11:30 PM

#

We've been using the the Pub keys until the end of last month - so, Make is still trying to communicate with those old keys. So weird. Thank you again

#jericho_api