Not enought fields info and Error 9123

[VitaliN]

Can you please give more detailed description for all request fields in api ATMs Inquiry 

In this case I can`t understand where I can get values for such fields
userId, userBid, requestMessageId(custom?), requestTs(custom?), useFirstAmbiguous

possible values of fields applicationId, distanceUnit, findFilters descriptions, operationName.

Whatever i do I have ERROR "Expected input credentials were not present"

[VitaliN]

Request details

Postman

Request Body

{

  "wsRequestHeaderV2": {

    "requestTs": "2021-08-11T01:49:53.887Z",

    "requestMessageId": "test1234567801",

    "userBid": "10000108",

    "applicationId": "VATMLOC",

    "userId": "CDISIUserID"

  },

  "requestData": {

    "distanceUnit": "mi",

    "distance": "60",

    "culture": "en-US",

    "options": {

      "range": {

        "count": 10,

        "start": 0

      },

      "operationName": "and",

      "sort": {

        "primary": "distance",

        "direction": "asc"

      },

      "useFirstAmbiguous": true

    },

    "location": {

      "geocodes": {

        "latitude": 46.4731455,

        "longitude": 30.7368612

      },

      "placeName": ""

    },

    "metaDataOptions": 0

  }

}

[jenn_kh]

Hi, and welcome to the Community, @VitaliN! An agent is looking into a solution for you and will get back with you shortly! If any community members know a solution, please feel free to respond in this thread -Jenn

[SLi]

Hi @VitaliN,

Please reference the X-Pay Token Guide for using API key-shared secret authentication method to connect to the API.

Please note that the resourcePath (in your Pre-request Script) for ATM Locator API should be /globalatmlocator/v1/localatms/atmsinquiry/

[VitaliN]

It doesn`t work. I used samples from API docs

[SLi]

Hi @VitaliN,

I've logged an internal ticket for our tech team to investigate and I will get back with an update as soon as I have one. Thanks.

[VitaliN]

Thanks @SLi 
Waiting for an answer

[SLi]

Hi @VitaliN,

There is an issue using X-Pay-Token authentication method to connect to the ATM Locator API. Our tech team is investigating and I will let you know once the issue has been fixed.

The APIs on Visa Developer support Mutual SSL authentication method as well. You can use this method to connect to the ATM Locator API and test in sandbox.

The tutorial below shows you how to create a project on Visa Developer with the Enhanced FX Rate API and test the API using Postman in Sandbox. Please watch this tutorial to get a step by step guide. While the tutorial uses the Enhanced FX Rate API, you can replace with the ATM Locator API instead.

https://community.developer.visa.com/t5/Tutorials/How-to-Connect-to-the-Visa-Enhanced-FX-Rate-API-us...

Please share screenshot if you experience any issues.