Does Global ATM Locator got a list of predefined tokens for the "placeName" property?

[agent_techhub]

Hi,

We are including Visa Global ATM Locator API into our solution. During development we paid attention, that some of locations, returned from the API contains, sort of, predefined tokens for the property "placeName": "ON STREET" and "RETAIL STORE". Since we are using the sandbox mode yet and have a restricted number of results, we cannot see if there are any other tokens. So the question - is there a list of such possible tokens? The reason of the question: in our use case, we should show a name of found ATM and showing "ON STREET" isn't a really good approach from our point of view. There is also property "ownerBusName", which be used alternatively, however for some other cases, this field has got a value, which is less meaningful and known to locals than "placeName". With the list we, at least, will have a chance to use its values in the condition and show either one, or another property. Or, maybe there is another approach, which we are not aware about? In this case we will be glad to hear it!

Thank you in advance!

[jenn_kh]

Thank you for reaching out, @agent_techhub! An agent will get back to you shortly! If any community members have a suggestion, please feel free to respond in this thread. - Jenn

[SLi · Accepted solution]

Hi @agent_techhub,

For sandbox testing, please use the test data that is provide on your Test Data tab of your project dashboard.

Please try the below API endpoint and request payload, you should see placeName and ownerBusName details (e.g.  "ownerBusName": "PNC BANK, NATIONAL ASSOCIATION", "placeName": "PNC BANK")

End Point https://sandbox.api.visa.com/globalatmlocator/v1/localatms/atmsinquiry
Method POST
Request
{
"wsRequestHeaderV2": {
"requestTs": "2021-10-25T18:28:18.000Z",
"requestMessageId": "ICE01-001",
"userBid": "10000108",
"correlationId": "909420141104053819418",
"applicationId": "VATMLOC",
"userId": "CDISIUserID"
},
"requestData": {
"distanceUnit": "mi",
"distance": "20",
"culture": "en-US",
"options": {
"findFilters": [
{
"filterValue": "C",
"filterName": "OPER_HRS"
},
{
"filterValue": "",
"filterName": "AIRPORT_CD"
},
{
"filterValue": "N",
"filterName": "WHEELCHAIR"
},
{
"filterValue": "N",
"filterName": "BRAILLE_AUDIO"
},
{
"filterValue": "N",
"filterName": "BALANCE_INQUIRY"
},
{
"filterValue": "N",
"filterName": "CHIP_CAPABLE"
},
{
"filterValue": "N",
"filterName": "PIN_CHANGE"
},
{
"filterValue": "N",
"filterName": "RESTRICTED"
},
{
"filterValue": "N",
"filterName": "PLUS_ALLIANCE_NO_SURCHARGE_FEE"
},
{
"filterValue": "N",
"filterName": "ACCEPTS_PLUS_SHARED_DEPOSIT"
},
{
"filterValue": "N",
"filterName": "V_PAY_CAPABLE"
},
{
"filterValue": "N",
"filterName": "READY_LINK"
}
],
"range": {
"start": 10,
"count": 20
},
"operationName": "or",
"sort": {
"primary": "city",
"direction": "asc"
},
"useFirstAmbiguous": true
},
"location": {
"address": null,
"geocodes": null,
"placeName": "700 Arch St, Pittsburgh, PA 15212"
},
"metaDataOptions": 0
}
}

[agent_techhub · Accepted solution]

Hello Stacey,

Thank you for the reply, but it doesn't answer to my question, unfortunately. Yes, I know about the "Test data" project's section. However, the ATM Locator API does accept geo coordinates as the search parameters, so it's pretty valid to use any correct coords there, isn't it? So I tried to use the following ones: [52.52, 13.4], which are Berlin's location (Berlin in Germany) and get back a list of results; it's even possible to do that in your Playground app, pls check the screen below.

Yes, I can't see all 2192 results, and this is understandable, because I'm in Sanbox, but should I recognize your answer as: we cannot rely on the data your API returns to us??? For some other coords I get empty list back, and this is also clear - Sandbox mode. But as soon as there are results - can't we use them for the development???

You mentioned in your answer, that I will see placeName and ownerBusName in API response. Ok, but I know it from the API documentation; the question isn't about presence of these properties in the response.

Best, Oleg.

[SLi · Accepted solution]

Hi @agent_techhub,

My apologies if my previous response did not answer your questions. The sandbox environment is designed to provide a general view and guide of the endpoint request and response structure. The data in the sandbox is preconfigured and covers a small set of possible requests. For the ATM Locator endpoint  https://sandbox.api.visa.com/globalatmlocator/v1/localatms/atmsinquiry, the valid test data is as below.

Regarding your question "we cannot rely on the data your API returns to us???"

Sandbox data is not live data, please do not use it to validate live ATM locations.

I hope this helps, please let me know of any further questions.

[agent_techhub · Accepted solution]

Hi Stacey,

Thank you for the response, first of all! Actually, it does contain exactly the reason, why I am looking for additional information: "The data in the sandbox is preconfigured and covers a small set of possible requests."; the data are preconfigured and doesn't describe most of real live situations, as I can imagine. However, while we are awaiting an access to the production data, I would like to implement as much as possible, based on the data, provided me with Sandbox access. And Sandbox does return some data to my request. I believe it's a separate question: why it does so?; it's not relevant for the topic. I don't know, what do you mean with "do not use it to validate live ATM locations", but I think I'm not use them in that manner; it's only to check how the live data might look like.

But Ok, let me rephrase my original question and ask the following:

The Global ATM Locator API defines the response property 'placeName'. What kind of an ATM's data will be returned there and are there some constant phrases like: "ON STREET", "OFFICE BUILDING", etc.?

It's neither about Sandbox, nor Production mode; it's about possible values which API might return there,

Thank you in advance!

Best, Oleg.

[SLi · Accepted solution]

Hi @agent_techhub,

Thanks for further explaining and I understand what you are looking for now. I have asked our product team to provide me a list of values for the 'placeName' field and will share the list as soon as I have it. Thanks.

[SLi · Accepted solution]

Hi @agent_techhub,

Thank you for your patience. Our ATM Locator product team let me know that the supported placeName tokens are defined in a 3rd party API which Visa calls and we don't have the details on these "Points of Interest" to share unfortunately. 

[agent_techhub · Accepted solution]

Hi Stacey,

Thank you for your efforts!

However, your team's response looks strange to me, to be honest... Does it mean, that the team uses 3rd party API without any documentation? And don't know what to expect from it? It's kind of strange for the financial institution, isn't it? Or you don't have a permission to share that info with someone who haven't got Production access yet? That's what I can understand. But still: your API does return some data and you don't know what the data are. Hmmm... not sure I can accept it as a solution.

Best,

[SLi · Accepted solution]

Hi @agent_techhub,

I appreciate the feedback and have asked our product team to share more information.