#kamon-identity-events
drowsy orbitBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- kamon000, 6 days ago, 16 messages
cerulean topaz
@torpid fable can you give me an example VerificationSession id so I can look at it?
kamon-identity-events
torpid fable
Here's one from one of my tests:
vs_1OZG7ZKq0PhFh4ntO281CReC
You can see that the events are there, but not attached to a webhook?
OH
You know what...I wonder if this is an issue.
That webhook is the "Connect" type
cerulean topaz
yeah that was what I was expecting
If you create the VS on your platform account the the Events will be sent to your Account WebhookEndpoint
torpid fable
Gotcha, that makes sense.
Can I update this webhook in Stripe to subscribe to both connect and normal events?
cerulean topaz
no those would be 2 completely separate WebhookEndpoints
torpid fable
Gotcha, will they have the same signing secret?
And can I handle them on the same API endpoint?
cerulean topaz
no they will have different signing secret since they are separate WebhookEndpoint. And you can use the same URL if that's what you meant by API though we usually recommend handling the two separately since they process different context
torpid fable
That makes sense.
If for some reason I were to have the webhooks have the same URL, is there a way to determine which signing secret to use?
because you construct the stripe event w/ the stripe webhook secret, so I'm wondering how to know which secret to use before that event is constructed
cerulean topaz
add a query parameter to the URL to distinguish them in your code