#Mike D-account.updated-event

1 messages · Page 1 of 1 (latest)

shadow portal
strong wave
#

hey there!

#

You shouldn't need to change anything on the account, but you will need to retrieve/list the accounts via the API

#

Retrieving/listing the account(s) should return data that includes the requirements and future_requirements for each one

glad matrix
#

Yes, we can get those accounts and have a list of users that have future_requirements. The problem is now that we have the webhook endpoint and logic in place, we need that webhook to fire again in order to sync everything up in our system. The webhook originally fired before we had the handler in place, so our API integration is out of sync with stripe. At this point, it would take a manual account change in order to fire off the webhook so it runs through our endpoint logic, updates our DB, flags the user as having requirements, and displays a banner on the front end to the end-user. I was hoping there was an easy way to re-fire the webhook.

strong wave
#

Not if the events are older than 30 days, no. And if they were within 30 days you'd still need to write a custom script to fire off stripe resend for each event ID. There is no bulk way to do that.

#

The simplest approach might be to iterate your accounts and update them to set a metadata entry to indicate this sync is done. eg metadata[synced_acct]: '2022-03-15' for each one

#

Which would produce a new account.updated event for each modified account

glad matrix
#

That's not a bad idea and gives me a few things to discuss with my team. Thanks for your help, I really appreciate it.

strong wave
#

NP!

#

(ie, don't try to fire off thousands of requests at once)

glad matrix
#

That's a good point, thank you for bringing that up