What's new
8 October 2026 (V6)
Changed
- The reference feature's vintage is now null, not "Unknown", when an address can't be matched or the source
has no year:
null in JSON, an empty Vintage element in XML, an empty field in CSV
and TSV, and no Vintage element in SOAP (generated clients read that as null). The source
stays "Unknown". If you test the vintage for "Unknown", test for null or empty instead.
Version 6.0 (October 2026)
New
- Geocoding V6 at
/Api/Geocode/V6/ (version=6.0), with the same parameters as V5
and output in JSON, XML, CSV, TSV or SOAP.
- 2015 census values:
censusYear=allAvailable now includes 2015.
- Exhaustive search:
exhaustiveSearch=true returns every candidate, not only the best match.
Changed
- An address that matches nothing gets the same answer in every format: NAACCR GIS coordinate quality 99 and
census tract certainty 99 (Unmatchable), micro-match status Non-Match, reference source "Unknown" and no
vintage (null). We no longer name one of the sources we searched.
- The reference feature's vintage is now text ("2024", or null when there is none), not a
number. If you read it as a number, update that before moving to V6.
- The micro-match status is filled in only with exhaustive search, except for an address that matches nothing
(Non-Match).
- SOAP clients: regenerate your client from the V6 WSDL.
Fixed
- An address that can't be matched no longer returns the center of a county in another state.
- SOAP answers include census values when you ask for them.
V6 documentation
· Moving from V5 to V6 (guide to come)
· API versions and retirement policy