#notamamasboy_v2-events-deliveries

1 messages Β· Page 1 of 1 (latest)

fringe skyBOT
#

πŸ‘‹ Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1442562345069973549

πŸ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

terse fog
#

Hello. πŸ‘‹

What is your question?

golden kernel
#

I guess my question is "can we expect to receive outbound payments event notifications if they are done on the dashboard platform

terse fog
#

Whether they are triggered by the Dashboard or an API request, the event should be emitted in both cases

golden kernel
#

My experience using the workbench is that the events that get created are not being sent to the webhook endpoint

terse fog
#

Looking at the event you shared, there are no endpoints configured to listen for it

golden kernel
#

how does one configure an endpoint for that event?

#

I have an event desitnation called "adventurous-sensation"

#

that should be listening to those event types

terse fog
#

The only webhook endpoints I see are Test/Live modes that both point to https://www.sfdominos.com/stripe/webhook

golden kernel
#

there is a /stripe/v2webhook endpoint for those events

#

Maybe it hasnt propagated correctly?

#

I can see it on the workbench, and like i mentioned I was able to ping it successfully

#

for example, this is the ping event evt_65TgQnrzlPK8PJCh8QT16P12Da1LSQVx6CrDa2ct9pwJzM

#

that hit the endpoint correctly

terse fog
#

Yes I can see that too

#

Can you test again to make sure these events are propagating correctly?

golden kernel
#

a payout?

#

or a ping?

#

I'll do a ping first

#

evt_65TgRP13sB2FG2BroQT16P12Da1LSQVx6CrDa2ct9pwAIy -> success

terse fog
#

I don't know what you mean by "ping". Stripe webhook event deliveries are POST requests from Stripe servers to the URL you specify.

golden kernel
#

yes, in the workbench you can trigger a ping event to the webhook

#

v2.core.event_destination.ping

#

I send another outbound payment : evt_65TgRQg9lPbYNEsyOhU16P12Da1LSQVx6CrDa2ct9pw2Hw
and still no i did not receive it on the same endpoint that I was able to get the ping event notification on

#

any help on this matter, would be greatly appreciated

terse fog
#

I'm still looking

golden kernel
#

thanks @terse fog

terse fog
#

Okay, I reached out to my colleagues and this is proving difficult to debug. Do you mind if we convert this to a Support case so we can debug async and get back to you?

golden kernel
#

absolutely

#

is there anything I need to provide to get this done

fringe skyBOT
#

Hello @golden kernel, we have sent you a direct message, please check it at https://discord.com/channels/@me/1442572976062201866

  • πŸ”—The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
terse fog
#

If you can just respond with the details to that DM, it will route directly to my team

golden kernel
#

will do thanks

#

the link just took me the the support center page

terse fog
#

There should be a box clicked to route directly to us

golden kernel
#

I guess because I had the assistant open previously I couldnt see the new support request

terse fog
#

I see the case!

#

I've got it

golden kernel
#

ok great

#

thanks @terse fog look forward hearing from the team

terse fog
#

Yeah, hopefully we can track this down

fringe skyBOT
#

notamamasboy_v2-events-deliveries

terse fog
#

Okay @golden kernel we did actually find something clear

#

But the events you are trying to receive are coming from your own account.

#

You should be listening to events_from: ["self"]

golden kernel
#

hmm

#

i dont see where I can configure that

#

should I create a new event destination maybe?

terse fog
#

You used the Dashboard for this so I'm not very familiar with those options. The team staffing this server focus on using the API where you can specify the events_from parameter

#

should I create a new event destination maybe?

Yes that will be required.

#

Once a webhook enpoint or event destination is set up, you cannot change whether it listens to other accounts or your own

golden kernel
#

I guess if theres an API for creating an event destination I can do it there

#

I guess my last question then

#

is whether or not you can use v2 accounts for self?

terse fog
#

I'm not sure what you mean by that

#

Like, I have a V1 Sandbox account that is configured to use the V2 APIs. I created an EventDestination on this Sandbox account and it sends V2 thin events to my server

golden kernel
#

hmm

#

i think the issue was the dashboard wording was a bit misleading

#

can I share a picture here?

terse fog
#

Sure

golden kernel
#

when I was reading in conjunction with the docs, they mentioned v2 api, so I guess I assumed that to receive those v2 thin event types I had to use the second option

#

and then of course, post creation, theres no way to tell that the webhook was setup incorrectly

terse fog
#

Yeah, first option is what you want. The second would mean you are receiving v2 events based on changes on separate accounts you are connected to

golden kernel
#

i just set it up like you mentioned

#

ill test and report shortly

terse fog
#

πŸ‘

golden kernel
#

it works

#

sorry for wasting your time

terse fog
#

It's not a waste, it's why we're here

#

and I'm glad you got it working

golden kernel
#

can I ask you a question about thin events? or would you rather I open up a new thread

#

its simply whether or not I can expect chronological order with the notifications event.type

#

or is that still not guaranteed

terse fog
#

That is still not guaranteed