- Need an Address Lookup service account and a ‘live’ click bundle.
- Replace underlying on-premise core / engine component with the client version as directed.
- Users migrating from standalone Atlas will only need to change the path parameter given to the AH50FH_Open function from a local pathname to a URL of the form.
http://tokenusername:tokenpassword@cloud.hopewiser.com/addrsvr[?maf=optional-maf-id]
Overview
AtlasClient API has an identical interface to the standard Atlas Development Kit (in terms of functions available) allowing on-premise integrations to switch to a web based solution (utilising a Hopewiser Address Lookup service account) by simply changing the underlying library.
AtlasClient API ships as part of the standard Atlas Development Kit, which includes complete documentation and sample integrations with various languages with a view to looking up, validating and formatting postal addresses and associated data. The development kit is not available as a download. To obtain a copy please contact us.
Demo
Quick Start Guide
Basics
Full documentation and guidance, as well as client wrapper components where applicable, are included in the AtlasClient developer toolkit section.
Customisations
No changes should be required from the traditional on-premise integration (unless additional functionality is required in making the switch).
Common Output Fields
Various, and dependant upon the referenced MAF (Master Address File). These are detailed in the accompanying documentation.