#jslaybaugh
1 messages · Page 1 of 1 (latest)
Duplication can occasionally happen. Is this once in a while or for all/most events?
every time
Can you share an example event ID?
evt_0MEFLCOc9qnPJL7OU7bVIVMO
I can see that there are two URL's under that event, but I don't know why... that first URL is for our connected platform. And then the second is also
OK its because your test standard account is connected to your platform in live and test mode, plus you have the same endpoint url configured for Live+Test and COnnect+Account
Yes, but not the same events
you should split up those endpoints in order to distinguish the events
What do you mean?
in the account, we only have 5 events filtered
and then for connected just 2
the only stuff we do for the connected accounts is this terminal stuff
sure, ok, ignore the account endpoints (but still i suggest using a different URL)
just within the connect endpoints, you have live and test using the same URL, same event types
why wouldn't I want that
I want live and test to all flow through the same code
and since this was a test transaction, it should just call the test endpoint
So you can more easily distinsguish test and live events
ok, that's decent advice, but it still doesn't explain why a test transaction is triggering a test event AND a live event
Yes, but in order to support some older integrations, connect events from live accounts using test mode Connect connections will send test mode events to both test and live mode endpoints, thats why you're seeing it twice
why would a test transaction trigger a live webhook
So if you change your URL to eg use ?mode=live and ?mode=test eg
you could filter out the live one and discard it
Legacy reasons - the event is labeled livemode=false though
It's test connections to live standard accounts -- that will also deliver test events you your live endpoints