Page 1 of 1

After doing this . When I try this events like sales order c

PostPosted: Wed Jan 10, 2024 3:12 pm
by kranil7701
Hi , I have added subscriptions .
here is the response :
[
{
"RecID": "235c49d3-6c13-4794-940c-e5d47578a63d",
"SY_WebhookSubscriber_RecID": "baf7e78f-f8ae-4ca8-ab08-f61ef978b38f",
"EventName": "salesorder.processed",
"URL": "https://topscripts.in/Steven/xero_api/process.php",
"ItemNo": 1,
"LastSavedDateTime": "2023-12-21T09:26:36.8400000",
"RowHash": "AAAAAAAGBcw="
},
{
"RecID": "6918a833-ea7f-439d-bb0e-1468a12f146c",
"SY_WebhookSubscriber_RecID": "baf7e78f-f8ae-4ca8-ab08-f61ef978b38f",
"EventName": "purchaseorder.created",
"URL": "https://topscripts.in/Steven/xero_api/process.php",
"ItemNo": 1,
"LastSavedDateTime": "2023-12-21T09:27:07.0800000",
"RowHash": "AAAAAAAGBc0="
},
{
"RecID": "be8af3eb-cf84-4a3d-925a-322ed0694d1f",
"SY_WebhookSubscriber_RecID": "baf7e78f-f8ae-4ca8-ab08-f61ef978b38f",
"EventName": "purchaseorder.updated",
"URL": "https://topscripts.in/Steven/xero_api/process.php",
"ItemNo": 1,
"LastSavedDateTime": "2023-12-21T09:27:25.2700000",
"RowHash": "AAAAAAAGBc4="
}
]


After doing this . When I try this events like sales order created I got no data on the urls which I have setup .
so please help me setup that .
thanks

Re: After doing this . When I try this events like sales ord  Topic is solved

PostPosted: Wed Jan 10, 2024 3:15 pm
by Mike.Sheen
What is your WebhooksHostURL system setting set to for the REST API?

Check the SY_WebHookMessage table to see if messages are being queued in there, if they are then check the SY_WebHookMessageResponse table to see what responses are being logged.

Examine the diagram on https://jiwa.atlassian.net/wiki/spaces/ ... 7/Webhooks to understand how the webhooks work.

Re: After doing this . When I try this events like sales ord

PostPosted: Wed Jan 10, 2024 3:30 pm
by kranil7701
Hi, Thanks for your response .
https://api-102329.austlink.cloud:4123/
This is the WebhooksHostURL url which currently setup under the setting .
But I want the webhook to send data at url https://topscripts.in/Steven/xero_api/process.php .
So do we need to change WebhooksHostURL to https://topscripts.in/Steven/xero_api/process.php to make it work ?
Or what else we can do so that the webhook will send data at https://topscripts.in/Steven/xero_api/process.php ?

Re: After doing this . When I try this events like sales ord

PostPosted: Wed Jan 10, 2024 4:10 pm
by Mike.Sheen
kranil7701 wrote:So do we need to change WebhooksHostURL to https://topscripts.in/Steven/xero_api/process.php to make it work ?


No, you do not.

The WebhooksHostURL looks correct, provided that is the URI of the REST API running.

What about the other things I said to check?

Check the SY_WebHookMessage table to see if messages are being queued in there, if they are then check the SY_WebHookMessageResponse table to see what responses are being logged.

Re: After doing this . When I try this events like sales ord

PostPosted: Thu Jan 11, 2024 7:27 am
by SBarnes
Two other things you may want to check also:

1. Can https://api-102329.austlink.cloud:4123/ be reached from the machines running the actual windows jiwa client, you can use a web browser to do this. If not it's probably a firewall issue

2. Check also that the the subscriber is also enabled as this information wasn't in your original post, this is in SY_WebhookSubscriber.

Re: After doing this . When I try this events like sales ord

PostPosted: Thu Jan 11, 2024 10:47 am
by Mike.Sheen
SBarnes wrote:Two other things you may want to check also:

1. Can https://api-102329.austlink.cloud:4123/ be reached from the machines running the actual windows jiwa client, you can use a web browser to do this. If not it's probably a firewall issue

2. Check also that the the subscriber is also enabled as this information wasn't in your original post, this is in SY_WebhookSubscriber.


I was getting to those - the outcome of the following question I asked:
Check the SY_WebHookMessage table to see if messages are being queued in there


Would have then led me to ask subsequent questions, relating to those two points you mentioned.

Based on the responses so far, it looks like we need to be asking for no more than one thing at a time to troubleshoot this.