[{ "id": "c219bc4f-8d2e-41da-9c0a-3819f5f66793", "createdDate": "2016-02-05T16:24:21.757", "eventType": "customer.subscription.created", "eventDate": "0001-01-01T00:00:00", "correlationId": "00000000-0000-0000-0000-000000000000", "payload": { "m1": "payload test" } { "_links": { "self": { "href": "rest/v1/notifications/c219bc4f-8d2e-41da-9c0a-3819f5f66793" } }, } }, { "notificationId": "636d12fe-8232-431c-82b3-fdf4019d7333", "createdDate": "2016-02-06T16:24:21.757", "eventType": null, "eventDate": "0001-01-01T00:00:00", "correlationId": "00000000-0000-0000-0000-000000000000", "payload": { "m1": "payload test" } { "_links": { "self": { "href": "rest/v1/notifications/636d12fe-8232-431c-82b3-fdf4019d7333" } } } }]
This JSON is shown in the Webhooks documentation but is invalid. Can we get an updated sample response, please?
Solved! Go to Solution.
โ03-07-2017 06:01 PM
Okay, here's a current sample:
{ "_links": { "self": { "href": "/rest/v1/notifications?offset=0&limit=100" } }, "notifications": [ { "_links": { "self": { "href": "/rest/v1/notifications/e35d5ede-27c5-46cc-aabb-131f10154ed3" } }, "notificationId": "e35d5ede-27c5-46cc-aabb-131f10154ed3", "deliveryStatus": "Delivered", "eventType": "net.authorize.payment.authcapture.created", "eventDate": "2017-02-09T19:18:42.167" } ] }
Not only is it valid, it represents what the system is actually returning. The previous sample had information in it that's not actually returned in the response, so it fails on two counts.
โ03-08-2017 08:55 AM
Hi John,
Sorry about that. We actually updated that sample a little while ago, along with a lot of other text on that page, but there's a veritable sausage grinder of build/stage/release steps that things go through before they hit the public web site. I'm not in the office right now, but when I get in, I can pull the updated samples and post them here.
โ03-08-2017 04:58 AM
Okay, here's a current sample:
{ "_links": { "self": { "href": "/rest/v1/notifications?offset=0&limit=100" } }, "notifications": [ { "_links": { "self": { "href": "/rest/v1/notifications/e35d5ede-27c5-46cc-aabb-131f10154ed3" } }, "notificationId": "e35d5ede-27c5-46cc-aabb-131f10154ed3", "deliveryStatus": "Delivered", "eventType": "net.authorize.payment.authcapture.created", "eventDate": "2017-02-09T19:18:42.167" } ] }
Not only is it valid, it represents what the system is actually returning. The previous sample had information in it that's not actually returned in the response, so it fails on two counts.
โ03-08-2017 08:55 AM
Thank you for the updated example. That will make development and testing much easier. :)
โ03-09-2017 05:05 AM
โ09-20-2018 02:59 AM
Hi All ,
We also have a postman collection for Webhooks REST APIs at https://github.com/AuthorizeNet/webhooks-postman-collection .
Hope it helps !!!
Thanks
โ09-20-2018 10:04 AM