Sandbox instance of the Travel Notification instance

[bpsymano]

Is VTNS down in sandbox? 

I and getting 404(s) when testing against the Sandbox environment. 

For "us",  VTNS has migrated to prod and not available in the Certification environment. "We" started to test Travel notifications (not testing in Prod) and consistently getting 404(s) when a few months ago this was not the case.

Questioning my sanity...

curl --location --request POST 'https://sandbox.api.visa.com/travelnotificationservice/v1/travelnotification/retrievetravel' \
--header 'Accept: application/json' \
--header 'Content-type: application/json' \
--header 'Authorization: Basic ###################################' \
--data-raw '{
   "retrieveTravelItinerary":{
    "fromDate":"2022-05-01",
    "toDate":"2022-05-29",
    "partnerBid": "10074101",
      "primaryAccountNumber":{
         "cardAccountNumber":"4121254490043929"
      }
   }
}'

[jenn_kh]

Thank you for reaching out, @bpsymano. An agent is looking into this and will get back to you as soon as possible. In the meantime, if anyone has any ideas that you feel may help, please share them here. -Jenn

[DianaVisaPM]

Hi @bpsymano,

To investigate the error, please provide the information below.

1. Endpoint
2. Request Header
3. Request Body
4. Response Header (include the x-correlation-id)
5. Response Body

Using SoapUI, you can find the x-correlation-id in the Raw Tab of the response header.