The basics
JSON or XML?
In this section, we will review the differences between JSON and XML responses. Both formats return the same ATM information, but some fields are written differently.
Example: One ATM in JSON and XML
JSON
{ "index": 0, "id": 2021, "atmIdentifier": "VSCU5972", "address": { "postalCode": "V7M2J3" }, "features": { "hours": 2, "driveThru": 0 }, "languages": ["en", "fr"]}XML
<location index="1" id="2021" atmCount="1"> <atmIds> <atmId>VSCU5972</atmId> </atmIds> <address> <postalCode>V7M 2J3</postalCode> </address> <features> <hours value="2">24 Hours a Day</hours> <driveThru value="2">No</driveThru> </features> <languages> <language id="en">English</language> <language id="fr">French</language> </languages></location>Difference between JSON and XML
Requesting JSON or XML
The request name and parameters are the same for both. Only the address changes.
https://api.ficanex.ca/service/json/ReturnAtmSearchByPostalCodehttps://api.ficanex.ca/service/service.asmx/ReturnAtmSearchByPostalCodeThe first address returns JSON and the second returns XML. Every request page also shows the SOAP version of the request. The ReturnAtm request is the only request with no XML or SOAP version.
SOAP Systems
SOAP tools build requests from the service’s description file, called the WSDL (Web Services Description Language), at /service/service.wsdl. The WSDL does not list bShowDuplicateAddresses. The service still accepts this parameter, but tools that build requests from the WSDL will not include it automatically.