VISA ATM api returns no data

[Uss_Defiant]

Hi, 

We're trying to get started with the VISA atm locator, but cannot seem to get any valid locations back from the API. Even the default query when one first loads the page returns no results (https://developer.visa.com/capabilities/atmlocator/reference#atmlocator__atmlocator__v1__atms_inquir...

I understand the response of:

• "statusCode": "CDIS203",
• "statusDesc": "Visa ATM Locator Svc-Failure (Empty Response Received from GMR)"

Indicates that we're hitting the sandbox and as such there's limited data. We've tried several locations however as suggested from the list here (https://community.developer.visa.com/t5/General/No-ATM-Found/td-p/6263) and are still getting the same response. Do you have a sample request I can use to successfully get one or more ATM results? 

[API_Managers]

Hi,

Thanks for being part of the Visa Developer Community! We have API Explorer available for you to start testing code. Please take a look at our API Explorer. API Explorer lets you choose the Product API, Endpoint and Method to see the Request and Response. Here is the link to API Explorer - https://developer.visa.com/apiexplorer

In addition to that, we also have sample code that is downloadable and also on GitHub. Please see the documentation link below.

Getting Started with Visa Developer > Getting Started Guide > Sample Code For Project

https://developer.visa.com/vdpguide#sample_code_for_project 

Please let us know if you have other questions or need further assistance. Or feel free to poke around the Visa Developer Community Forum for a large abundance of questions and answers that may relate to your point in question. 

Thank you,

Diana

[mobility23]

I was facing the same Problem. Since moderator's generic answer is not helpful at all, I found out that a request using "geocodes" with Lat/Lng didn't worked. However, using "placeName" instead worked for me. Although "geocodes" with Lat/Lng is marked as "required" and "placeName" is marked as "optional" in the Documentation, it seems like it's the the other way around.

Documentation should be fixed!