/autocomplete/addresses now accepts a context= argument which allows additional countries to be searched. This currently defaults to GBR but also accepts USA
New autocomplete/addresses/:id/gbr API which resolves address suggestions to the GBR address format (regardless of country)
The standard GBR address objects now also return an id attribute
The standard GBR address object now also returns a dataset attribute which identifies the provenenace of a result (e.g. paf means Postcode Address File, mr means Multiple Residence and nyb means Not Yet Built)
The standard GBR address object now also returns a country_iso which returns the 3 letter ISO country code
/addresses and /autocomplete/addresses now accepts query arguments to bias results by a geospatial area defined by an origin (WGS84 coordinate) and radius (in metres) with bias_lonlat=[longitude],[latitude],[radius]
/addresses and /autocomplete/addresses now accepts query arguments to filter results by a geospatial box defined by an "top-left" and "bottom-right" WGS84 coordinates. Filter addresses with box=[top left longitude],[top left latitude],[bottom right longitude],[bottom right latitude]
/addresses and /autocomplete/addresses now accepts query arguments to bias results by a geospatial area defined by an origin (WGS84 coordinate) and radius (in metres) with bias_lonlat=[longitude],[latitude],[radius]
/addresses and /autocomplete/addresses now accepts query arguments to filter results by a geospatial box defined by an "top-left" and "bottom-right" WGS84 coordinates. Filter addresses with box=[top left longitude],[top left latitude],[bottom right longitude],[bottom right latitude]
/addresses and /autocomplete/addresses now accepts query arguments to bias results by locality or postcode elements like post_town or postcode_sector with bias_post_town= and bias_postcode_sector=
/postcodes/:postcode now returns up to 5 suggested postcodes if there is no exact postcode match. It will check for common errors first (i.e. mixing up 0 and O or 1 and I).
Checking key details with the /keys/:key will now return a datasets attribute. This identifies which datasets (i.e. PAF, Multiple Residence, Not Yet Built) this key has access to.
Licensee keys may now be passed in via the API Key argument of the querystring (api_key=) or authorisation header IDEALPOSTCODES api_key="". Our documentation will be updated to reflect this as the primary method of identifying a licensee. However the earlier method of supplying both licensee and api_key will continue to be supported.