topic Re: /rest/v1/notifications/{notificationId} gets "The requested resource could not be found&amp in Integration and Testing

/rest/v1/notifications/{notificationId} gets "The requested resource could not be found"

jonCherlin1 — Wed, 02 May 2018 19:40:26 GMT

I am currently using Postman for testing.

When I GET https://apitest.authorize.net/rest/v1/notifications/ I receive all my notifications such as the following...

"notifications": [
        {
            "_links": {
                "self": {
                    "href": "/rest/v1/notifications/3c60e0e6-354a-409c-8e4e-4f04a718f14d"
                }
            },
            "notificationId": "3c60e0e6-354a-409c-8e4e-4f04a718f14d",
            "deliveryStatus": "Delivered",
            "eventType": "net.authorize.payment.void.created",
            "eventDate": "2018-04-23T22:20:09.93",
            "webhookId": "5d5819f9-bae5-4e7b-b9b7-694646b1c10e"
        },

However, I want to get the "payload" so I can get the transaction id. I saw in another post https://community.developer.authorize.net/t5/Integration-and-Testing/Notification-History-Payload/m-p/59122/highlight/true#M33723 that, in order to do that you just /rest/v1/notifications/{{notificationId}} . I tried this a couple of weeks ago and it worked fine...but now, for example, if I try to GET https://apitest.authorize.net/rest/v1/notifications/3c60e0e6-354a-409c-8e4e-4f04a718f14d it returns...

{
    "status": 404,
    "reason": "NOT_FOUND",
    "message": "The requested resource could not be found.",
    "correlationId": "3a2707c9-3e4e-4bae-a17b-9da0b6247d08"
}

Any idea what might be wrong? Could it be something is wrong on Authorize.net's end? Or am I just doing something wrong somehow?

Re: /rest/v1/notifications/{notificationId} gets "The requested resource could not be found&quo

jonCherlin1 — Wed, 02 May 2018 20:14:54 GMT

Update:

I attempted to make a new Transaction and see if I could get the payload with one of the new notification ids and it works. However, if I try to do it for the older notifications (such as from April 24th) it still doesn't. Is there some kind of expiration on these notifications?

Re: /rest/v1/notifications/{notificationId} gets "The requested resource could not be found&

Anurag — Thu, 03 May 2018 06:16:16 GMT

Hi @jonCherlin1

Thanks for updating on it .

Looks like this is a bug in the API which is restricting the fetch of older notifications .

The team is looking into the fix and will update soon.

Thanks

Re: /rest/v1/notifications/{notificationId} gets "The requested resource could not be found&

jonCherlin1 — Thu, 03 May 2018 14:05:19 GMT

Anurag Thank you so much! Please keep me updated.

Re: /rest/v1/notifications/{notificationId} gets "The requested resource could not be found&

jonCherlin1 — Mon, 21 May 2018 19:08:50 GMT

Has there been any progress on this? I still can't fetch older notifications.

Re: /rest/v1/notifications/{notificationId} gets "The requested resource could not be found&

Anurag — Tue, 22 May 2018 05:29:03 GMT

The fix is done and its going through the QA cycle .

will update once we have a release date for it .

Thanks

Re: /rest/v1/notifications/{notificationId} gets "The requested resource could not be found&

jonCherlin1 — Tue, 22 May 2018 14:39:50 GMT

Thank you!! Please let us know.

Re: /rest/v1/notifications/{notificationId} gets "The requested resource could not be found&

rajvpate — Mon, 16 Jul 2018 21:10:29 GMT

Hi,

Please try now. You should no longer see 404 for your scenario.

Thanks,

~ Rajvi Patel