#db-connect-webhook

1 messages · Page 1 of 1 (latest)

tacit ravineBOT
wild quarry
#

db-connect-webhook

#

@bleak blaze there's no specific recommendation in this case honestly, that depends a lot on your overall codebase and how separate the code for your own integration is from the Connect platform features.

#

If it were me I'd have 2 separate endpoints/URLs

bleak blaze
#

hmm, alright. yeah i think separating them would make it easier to reason about. however, there are only a few events for connect accounts that ill be listening to and i guess thats what im getting at.

wild quarry
#

sure but having 2 separate code for this makes sense. They have different logic (one has an `account property), they'll have a different signing secret

bleak blaze
#

yeah i did notice the account property. but for the signing secret - i think we can use the same one from 1 webhook url, no?

wild quarry
#

No you can't. Each webhook endpoint has its own secret

bleak blaze
#

oooh i think youre saying that each webhook url (regardless of type of account) has its own signing secret?