Good Day to all. I am trying out the Xero webhook in a local setup.
Environment:
Node js backend
Using Ngrok for hosting the endpoint publicly
Xero Trial Account
I was able to successfully set up the webhook. My service received 3 unauthorized (401) calls and 1 successful (200) call, which made the ITR status OK.
However, after the ITR success, I tried creating a contact, updating an existing contact and updating an invoice and waited for nearly 10 to 15 minutes and I did not receive any events to the webhook endpoint.
Not sure if I have missed any steps? Any pointers to why I am not receiving the events?
Is there any way I can see if the events that are fired from the Xero side?
Does the webhook work only for Partner apps?
Not sure what I am missing here. Appreciate any help on this.
Cheers!
Can you confirm that your Trial organisation is connected to the app? If not, following the Postman tutorial will ensure that it is connected.
https://developer.xero.com/documentation/tools/postman
Related
I am currently working on a React website and NodeJS API that implements the Stripe API to allow payments. The user can subscribe to 3 different plans and get different access depending on the chosen plan.
I have already set up the webhook endpoint URL in my stripe account and there is no problem about that. I am getting webhooks and I manage my database depending on the event type.
My problem is that I want to update my frontend as soon as a payment succeeded for example when the invoice.payment_succeeded is triggered. But the fact that this is a webhook to a POST route, I can not send back a responses to my client. I was wondering if there is actually a way to send back data after a webhook.
Thanks to anyone who can help me.
Implement a web socket connection.
send data to the web socket as soon as you receive invoice.payment_succeeded from the webhook.
implement socket client in the react app to listen to the data send from the server.
I am using the official DocuSign java client 3.2.0. I have set the envelope level notification as listed below. Say the webhook URL is https://A.
EventNotification eventNotification = new EventNotification();
eventNotification.setIncludeHMAC("true");
eventNotification.setIncludeDocuments("true");
eventNotification.setRequireAcknowledgment("true");
eventNotification.setUrl("https://A");
EnvelopeEvent envelopeEvent = new EnvelopeEvent();
envelopeEvent.setEnvelopeEventStatusCode("completed");
eventNotification.setEnvelopeEvents(Arrays.asList(envelopeEvent));
envelopeDefinition.setEventNotification(eventNotification);
I am trying to test the retry logic for this webhook. After few successful push requests, I intentionally made the service to return non 200 code (Example 404) for one of the request. Then I reverted the logic, so that the service continue to return 200 response for new requests.
I checked after more than 24 hours, the failed request was never retried.
Is there any reason why the request was never retried eventhough there were successful requests after the failure?
I also have a connect listener configured to push the complete notification for all the envelopes to webhook URL https://B
Currently we have come issue with this webhook URL, so all the push notification to https://B is getting failed.
Is the continuous failure with the https://B connect webhook stop retries to envelope level notification webhook https://A ?
Also Is there any difference between the connect retry vs envelope notification retries?
For for global account events (all users and envelopes) make sure "Require Acknowledgement" option is selected in your Connect settings for the specific webhook for the failed to be re-pushed.
Connect webhook is global (all users and envelopes) for the account and you can select when is triggered for example "Envelope Sent", "Envelope Voided" etc. In this way you can have multiple webhooks handling different account events.
In your case you are setting webhook notification only for the specified envelope.
Also this could help you
https://developers.docusign.com/docs/esign-rest-api/reference/Connect/ConnectEvents/
Connect retries at the account level for Aggregate Messages (the default) after 24 hours after a subsequent message is sent. I will ask about envelope-level connect retries.
Better is to switch to Send Intermediate Messages (SIM) queuing. It retries faster.
Best is to have a 100% always up listener (server). An easy and cheap (free) technique for this is to use AWS PaaS to receive and enqueue the messages. See blog post and sample code. We also have sample code for Google Cloud and Azure.
I am using the DocuSign Rest API v2. During envelope creation process, we will send our rest API URL to receive the notifications.
The events are properly receiving in our live setup. But in our local development setup we are not receiving the notifications.
For this, we have whitelisted the IP ranges mentioned in the DocuSign Page on our side.
https://trust.docusign.com/en-us/trust-certifications/ip-ranges/
But still, we are not receiving notifications to the development setup.
What else we need to do to get this done?
Unfortunately I'm unable to respond to the original post, however I've experienced the same issue (reported here). It only appears to occur when envelopes are sent as far as I can tell, and I'm able to retrieve the status afterwards - but it's not in line with what the API guide tells us, nor what was happening previously.
I registered for Evernote webhook successfully with a valid end point recently. But whenever I make any changes to my evernote account, either by creating or updating a note, I am not being notified by the webhook. I am using a page created with http://requestb.in/ as an endpoint but I don't see evernote making any requests to it. I have reached out to Evernote support but haven't received a response yet.
How do you test to see if Evernote Webhook is working as expected?
The easiest way is to check the web logs of the web server you've set up to receive them.
I have a couple of web hooks set up and they seem to work. I've used a node.js app to receive the webhooks.
Double-check that you asked for the right kinds of notifications? What filter did you ask for?
Other than double-checking the URL you gave them, and double-checking the logs, and if using https ensuring you are using a valid certificate, there isn't much else other than waiting for the support response.
In the meantime you can test your code by hitting your webhook server with appropriately formatted URLs.
We have been using 2checkout as one of a payment providers for a while now. We run a subscription based service that activate a set amount of time on the users account when we receive a notification.
For some reason in the past few days a number of users (not all) have been receiving notifications of Order Created 3 times, 1 every half an hour.
This is giving then 3 times their purchased time on our system.
Does anyone have any idea why this is happening?
I originally thought it was a case of waiting for the fraud status as on one account, the status was 'wait' for the first 2 notifications. But I have now seen with other users that the fraud check has passed on all 3 notification.
Any help would be appreciated.
Cheers
Nadeem
2Checkout INS notification will attempt to retry for a total of 3 attempts if a successful HTTP response is not returned by your server. You should be able to confirm that they are failing by checking the Failed logs in your 2Checkout account under the Notifications tab. Please contact 2Checkout tech support at techsupport#2checkout.com for assistance with troubleshooting the issue. They will be able to pull the logs to show the response from your server when the notification fails.