#aeropuertomc_webhooks
1 messages ยท Page 1 of 1 (latest)
๐ 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/1480550671941107956
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- aero_webhooks-fc, 2 days ago, 13 messages
- aeropuertomc_webhooks, 2 days ago, 10 messages
- aeropuertomc_webhooks, 3 days ago, 21 messages
Hello ๐ taking a look!
I see your last few Discord threads were about the same topic and referenced the same event that is past our retention of delivery details. Did you try writing into support as suggested? Do you have a new question?
Hi, yes, we wrote to Support. They suggested us to implement the webhook listener. We launched the listener to production today, but we are not seeing the webhook triggered for some accounts.
What are you doing to trigger the event? Do you have the financial connections account ID or the request ID to to update the account number?
Yes. It is: fca_1SwUCZG3Bht1LHJQ9Cf2fNKG
The user added the account but it came in with null account number. We talked to support and they said that it might take a bit to retrieve the numbers.
That we should listen to the number update event to catch it later
Taking a look
I'm not finding much here. I think the path forward is pushing on our support team to look further into this. It looks like you are creating the session properly from the API which is most of what this server can look in to, beyond that it is hard for me to tell how this is supposed to work.