ATM locator : foundATMLocations always null

[Marco]

Hello,

We are facing a problem with ATM locator API. With the API explorer and the sample request we always have no ATM found. We try many request but the field "foundATMLocations" is always null. And if I understand the doc "foundATMLocations" should not be null.

Below a request with "foundATMLocations" = null:

POST

https://sandbox.api.visa.com/globalatmlocator/v1/localatms/atmsinquiry

BODY

{
  "requestData": {
    "culture": "en-US",
    "distance": "500",
    "distanceUnit": "mi",
    "metaDataOptions": 0,
    "location": {
      "address": null,
      "placeName": "700 Arch St, Pittsburgh, PA 15212",
      "geocodes": null
    }
  }
}

RESPONSE :

200 OK

HEADER :

server: Apache
x-served-by: l73c035
x-correlation-id: 1534278456_352_77_l73c035_VDP_ARM
x-backside-transport: OK OK,OK OK,OK OK,OK OK
x-global-transaction-id: 583212481
x-app-status: 200
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
strict-transport-security: max-age=2592000;includeSubdomains
cache-control: no-cache, no-store, must-revalidate
pragma: no-cache
expires: -1
content-type: application/json;charset=UTF-8
content-language: en-US
content-length: 973
date: Tue, 14 Aug 2018 20:27:37 GMT
connection: close

RESPONSE BODY :

{
"responseData": [
{
"metaData": null,
"matchedLocations": [],
"foundATMLocations": null,
"distanceUnit": null,
"totalATMCount": 0,
"bestMapView": null,
"properties": null
}
],
"wsResponseHeader": null,
"wsStatus": {
"statusCode": "CDIS203",
"statusDesc": "Visa ATM Locator Svc-Failure (Empty Response Received from GMR)"
},
"wsResponseHeaderV2": {
"requestMessageId": "VATMLOC54264-20180814202736400",
"correlationId": "VATMLOC4653120180814202736400",
"responseMessageId": "51VATMLOC180520180814202736401",
"numOfRowsReturned": 0,
"responseTs": 1534278457078
},
"responseSummaryData": null
}

[API_Products]

Hi @Marco,

Please submit the CSR form and file so that we can get you access to the production data. To learn more about how to submit the CSR form and file, please navigate to this link. https://developer.visa.com/pages/going-live#client_onboarding_form

The sandbox environment does not have data for all the ATM Locations. The response ‘CDIS203’ is not failure, but valid response where the search didn’t result in any locations.  

In the US, we have chosen locations in the state of Pennsylvania for testing, also, following are the cities where you may query for ATM locations worldwide.
 
PHILADELPHIA, SHANGHAI, BEIJING, LONDON, MADRID, SAO PAULO, BERLIN, PARIS, PITTSBURGH, MUMBAI, MOSCOW, TOKYO, TORONTO, VANCOUVER, DUBAI, HARRISBURG, ALLENTOWN, READING, LANCASTER, ERIE, PHILA, MANILA, YORK, BELEM, SYDNEY, ROME, BETHLEHEM, WASHINGTON, KIEV, WILKES BARRE, STATE COLLEGE, WEST CHESTER, GREENSBURG, SCRANTON, BENSALEM, WILLIAMSPORT, UPPER DARBY, LEBANON, NORRISTOWN, ALTOONA, EASTON, NEW CASTLE, JOHNSTOWN, CHESTER, UNIONTOWN, BUTLER, MONROEVILLE, CARLISLE, MCKEESPORT, LEVITTOWN, MECHANICSBURG, WILKES-BARRE, CHAMBERSBURG, WEST MIFFLIN, LATROBE, POTTSTOWN, KING OF PRUSSIA, LANSDALE, ALIQUIPPA, CORAOPOLIS, EXTON, HANOVER, ANANINDEUA, DOYLESTOWN, HAZLETON, MEDIA, CAMP HILL, WARMINSTER, CONSHOHOCKEN, BEAVER FALLS, BETHEL PARK, WILLOW GROVE, GETTYSBURG, KITTANNING, MONACA, INDIANA, NEW KENSINGTON, SPRINGFIELD, WAYNE, BLOOMSBURG, BRIDGEVILLE, LANGHORNE, PHOENIXVILLE, CANONSBURG, WHITEHALL, MEADVILLE, QUAKERTOWN, BRISTOL, STROUDSBURG, PITTSTON, CONNELLSVILLE, CARNEGIE, COATESVILLE, LOCK HAVEN, BRADFORD, IRWIN, KUNKLETOWN, MCKEES ROCKS, ELIZABETHTOWN, LITITZ
 
The responses you are seeing below are not failures, but valid responses where your search didn’t result in any locations. If you see any return status other than "CDIS203", then please alert us and we’d be happy to look at.

[Marco]

Hi Diana,

Thank you for your quick reply. 

I understand the sandbox environment does not have data for all the ATM locations and the response CDIS203 is a success.

But you explain the sandbox env have ATM locations data for somes places like PHILADELPHIA, SHANGHAI, BEIJING, …

I tried with these places but the response field "foundATMLocations" is still null.

So can you give me a request example where I can have ATM locations data ? Or it is impossible to have "foundATMLocations" not null with the sandbox env ? 

[API_Products]

Hi @Marco,                             

To further investigate, please provide the following information:

1. End Point
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.

[Marco]

Hi @DianaTran-Yee

Below you can found information about the request for ATM location in Paris but with foundATMLocations = null.

Is there a way to have foundATMLocations not null in sandbox env ?

// REQUEST// URLPOST

https://sandbox.api.visa.com/globalatmlocator/v1/localatms/atmsinquiry

// HeaderAccept: application/jsonAuthorization: {base64 encoded userid:password}

// Body

{

• "wsRequestHeaderV2": {
  • "requestTs": "2018-08-16T18:50:43.000Z",
  • "applicationId": "VATMLOC",
  • "requestMessageId": "ICE01-001",
  • "userId": "CDISIUserID",
  • "userBid": "10000108",
  • "correlationId": "909420141104053819418"
  },
• "requestData": {
  • "culture": "en-US",
  • "distance": "500",
  • "distanceUnit": "mi",
  • "metaDataOptions": 0,
  • "location": {
    • "address": null,
    • "placeName": "Paris, FRANCE",
    • "geocodes": null
    }

}}

// GENERATED RESPONSE

200 OK

// Header

server: Apache

x-served-by: l73c001

x-correlation-id: 1534445567_891_91_l73c001_VDP_ARM

x-backside-transport: OK OK,OK OK,OK OK,OK OK

x-global-transaction-id: 10948591

x-app-status: 200

x-frame-options: SAMEORIGIN

x-xss-protection: 1; mode=block

x-content-type-options: nosniff

strict-transport-security: max-age=2592000;includeSubdomains

cache-control: no-cache, no-store, must-revalidate

pragma: no-cache

expires: -1

content-type: application/json;charset=UTF-8

content-language: en-US

content-length: 10556

date: Thu, 16 Aug 2018 18:52:48 GMT

connection: close

// Body

{

• "responseData": [
  • {
    • "metaData": null,
    • "matchedLocations": [...]// 25 items,
    • "foundATMLocations": null,
    • "distanceUnit": null,
    • "totalATMCount": 0,
    • "bestMapView": null,
    • "properties": null
    }
  ],
• "wsResponseHeader": null,
• "wsStatus": {
  • "statusCode": "CDI000",
  • "statusDesc": "Visa ATM Locator Svc-Success"
  },
• "wsResponseHeaderV2": {
  • "requestMessageId": "ICE01-001",
  • "correlationId": "909420141104053819418",
  • "responseMessageId": "51VATMLOC5969620180816185247962",
  • "numOfRowsReturned": 25,
  • "responseTs": 1534445568286
  },
• "responseSummaryData": null

}

[API_Products]

Hi @Marco,                              

Sandbox data is limited and does not reflect a real live production environment. Each project is assigned test data values particular to their project that can be accessed by clicking on the following highlighted links within the project:

                                                                      

[Marco]

Hello @DianaTran-Yee,

I understand sandbox data is limited and now I know i can see available sandbox data  on Test Data / ATMs Inquiry page. 

But I am still not able to have foundATMLocations != null. I tried with all places listed under Test Data / ATMs Inquiry page

1 Bigelow Square, Pittsburgh, PA 15219

Allentown, PA

1414 S Penn Square, Philadelphia, PA 19102

237 7th St, Pittsburgh, PA 15222

700 Arch St, Pittsburgh, PA 15212

So my question: Is that possible to have foundATMLocations not null ? If yes, can you give me a request example ? If no can you confirm me that in Sandbox env this is not possible to have foundATMLocations not null.

Thank you for your help 🙂

[API_Products]

Hi @Marco,

I will take a look and get back to you soon!

[Marco]

Hello Diana,

Any news about atm data on Sandbox env ?

[API_Products]

Hi @Marco,

Per the design, it is possible that foundATMLocations is null, in the case, there is no ATM data for the given input address/location.

Besides that, there was an issue in the Sandbox environment that was recently resolved so you should now be able to get “foundATMLocations” for the approved test data.