Skip to main content

Changelog

Stay informed about the latest updates and improvements to our address validation services with our changelog. View release notes and see what's new.

April 2026​

  • [Browser Extension] Improved Odoo and Salesforce field detection (2026-04-29, v1.25.4)
    • Address Finder now waits for new Odoo contact forms to finish initialising before binding to address fields
    • Salesforce scope selectors updated for custom Aura components
  • [Billing] Credit notes available in your account (2026-04-28)
    • View credit notes alongside invoices from the billing section
  • [Billing] Statement of account (2026-04-28)
    • Download a consolidated statement of invoices, payments, and credit notes for any period
  • [Dashboard] Organisation deletion (2026-04-27)
    • Permanently remove an organisation and its data from your account when it is no longer needed
  • [Dashboard] Multi-organisation accounts (2026-04-24)
    • Switch between organisations from a single login
    • Single-organisation users are routed straight to their organisation page on sign-in
  • [Billing] Reduced 3D Secure (SCA) prompts on automated top-ups (2026-04-23)
  • [Data] Corrected ISO 3166-1 alpha-3 country code for Kosovo (2026-04-23)
  • [Dashboard] New URL checker tool for Allowed URLs (2026-04-16)
    • Test whether a given domain matches your account's allowed URL configuration before going live
  • [Dashboard] Documentation search integrated into the dashboard (2026-04-14)
    • Search docs.ideal-postcodes.co.uk directly from your account using DocSearch
  • [Data] Fixed Republic of Ireland address line formatting on HERE datasets (2026-04-08)
  • [Logging] CSV transaction usage export now includes a licensee name column (2026-04-02)
  • [Authentication] Passkey (WebAuthn) sign-in (2026-04-01)
    • Sign in using Touch ID, Windows Hello, or hardware security keys instead of a password

March 2026​

  • [Dashboard] Dashboard UI refresh (2026-03-27)
    • Redesign with dark mode, smooth theme transitions, and modernised screens
    • Improved pagination and notification UX
  • [Dashboard] Account notifications (2026-03-26)
    • In-dashboard notification bell surfacing recent account events, with email recipients managed per organisation
  • [Dashboard] Per-dataset toggles on the API key dashboard (2026-03-26)
    • Enable or disable individual datasets on a key directly from the keys page
  • [API] GET /keys/:key/details returns expanded key metadata (2026-03-25)
    • Response now includes name, contexts, datasets, and notification settings
  • [Address Finder] New hide configuration option (2026-03-20, v5.2.10)
    • Dynamically hide and style additional HTML elements when the finder is collapsed
  • [Dashboard] Self-serve organisation creation (2026-03-11)
    • Create new organisations from your account without contacting support

February 2026​

  • [Dashboard] Organisation member invitations (2026-02-25)
    • Invite teammates to your organisation by email and review pending invitations from the organisation page
  • [Dashboard] Organisation accounts (2026-02-20)
    • Accounts are now organisation-based — invite teammates, share API keys, and assign roles within a single billable entity
  • [Dashboard] Account roles: admin, developer, and finance (2026-02-20)
    • Assign each organisation member a role to scope access to keys, billing, and developer settings
  • [API] Monthly lookup limits now configurable on API keys (2026-02-04)
    • Set a per-calendar-month cap independently of the daily limit, with usage rolling over at the start of each month

December 2025​

  • [Data] Added the BEV (Bundesamt für Eich- und Vermessungswesen) dataset for Austria, providing comprehensive and authoritative address coverage
  • [Data] Postcodes.io LSOA and MSOA fields now return 2021 Census data. 2011 data available via lsoa11/msoa11 aliases
  • [Data] Postcodes.io ONSPD updated to November 2025
  • [API] Postcodes.io now returns terminated postcode data in 404 responses

November 2025​

  • [API] New dataset filter parameter allows you to restrict address searches to specific datasets within a country. E.g. datasets=nyb for latest new builds only.
  • [API] New GBR postcode query endpoint for UK postcode lookups
  • [API] Improved AddressBase Core searching, now harmonized with other GBR datasets for consistent results
  • [API] US Address Validation API now supports fuzzy matching on the state parameter, improving match rates for addresses with minor state name variations

October 2025​

  • [Data] Northern Ireland dataset update frequency increased from quarterly to weekly
  • [API] Non-US address data now parsed into individual structured fields (building number, street name, unit) rather than just address lines
  • [Data] Fixed an issue affecting Republic of Ireland addresses where administrative data may be missing for some premises

September 2025​

  • [API] Streamlined OpenAPI specification designed to reduce context length for LLM-assisted development
  • [Documentation] LLM-optimized documentation with llms.txt context file and universal markdown export (add .md to any documentation URL)
  • [Integration] WooCommerce plugin now available for WordPress e-commerce stores with no-code installation from the WordPress Plugin Directory
  • [Integration] Documentation now available through Context7's Model Context Protocol (MCP) for AI-enabled IDEs
  • [API] Enhanced geospatial accuracy and intelligent country detection for improved search precision
  • [Data] Postcodes.io County Electoral Divisions updated to May 2025
  • [Data] Postcodes.io Parish/Non-Civil Parish codes updated to April 2025

August 2025​

  • [API] Fixed an issue with the Email Validation API to handle queries without proper encoding

July 2025​

  • [API] CSV usage log export now includes a lookups column showing how many lookups each request consumed. See the CSV usage log API for details.
  • [Performance] JavaScript libraries now served directly from the API for improved caching, reduced latency, and simplified integration

June 2025​

  • [Data] Improved Republic of Ireland coverage for the standard dataset. All addresses now include Eircode (Irish postal codes)
  • [Documentation] Documentation site now generates an LLM.txt file and .md files to better support language model integration
  • [API] Improved handling of ordinals and directionals for US addresses

May 2025​

  • [Data] Improved and extended UPRN matching for Royal Mail Multiple Residence and Not Yet Built addresses
  • [Data] Additional HERE datasets included
  • [Data] Localised and improved South Korea coverage with MOIS dataset

April 2025​

  • [Data] Localised and improved Belgium coverage with FODBOSA
  • [Data] Localised and improved Japan coverage

March 2025​

  • [API] Maximum allowed configurations increased to 64. Maximum payload size for each configuration object increased to 64kb

February 2025​

  • [Data] Expanded Canada coverage with Canada National Address Register dataset

January 2025​

  • [Data] Expanded Denmark coverage with SDFI dataset

May 2024​

  • [API] Released /addresses/verify API for USA CASS Verification

April 2024​

  • [Data] Netherlands (Kadaster) address dataset incorporated
  • [Data] Norway (Kartverket) address dataset incorporated
  • [Performance] Improved P95 and P99 latency

March 2024​

  • [Data] AddressBase searches can now be filtered by property classification type (e.g. Commercial, Residential, Military, etc). See AddressBase data documentation for more information.

February 2024​

  • [Data] Search improvements for Iberian languages: Spanish, Catalan, Galician and Basque
  • [Address Finder] Country selection is synced if country: is defined in outputFields

January 2024​

  • [Data] Australia GNAF address dataset added
  • [API] CASS Certified USA address verification generally available

November 2023​

  • [Data] Improvements to geospatial biasing for USA addresses

October 2023​

  • [API] Key settings can be updated via POST /keys/:key API
  • [API] Available datasets accessible through GET /keys/:key/details API
  • [Address Finder] Added the ability to fix Address Finder

September 2023​

  • [Address Finder] Added new callback for changes in country or context
  • [Address Finder] Country is automatically detected by IP address

August 2023​

  • [Data] Hong Kong dataset included
  • [Data] Macau dataset included
  • [Data] Taiwan dataset included
  • [Data] India dataset included

July 2023​

  • [Data] Asia Pacific data now available
  • [Data] Oceania dataset included

June 2023​

  • [Data] South America data now available
  • [Data] Middle East & Africa dataset included

May 2023​

  • [Data] Eastern Europe data now available

April 2023​

  • [Data] Western Europe data now available for Address Finder

March 2023​

  • [Data] Improved Zip and ZIP+4 searching on USA datasets
  • [Data] Improved apartment searches for GBR datasets

February 2023​

  • [Data] AddressBase Core data now available for GBR address search

January 2023​

  • [API] /postcodes/:postcode API now returns Eircode addresses if enabled on your account
  • [Data] Rooftop geolocations now available for Northern Ireland. Please contact us to have this enabled on your account
  • [Data] UPRNs now available for Northern Ireland. Please contact us to have this enabled on your account
  • [API] /addresses/cleanse GBR Cleanse API now available

December 2022​

  • [API] Phone Validation API now generally available
  • [Data] UK post towns are now titlecased (instead of all caps)
  • [API] Republic of Ireland addresses can be retrieved via the /postcodes/:postcode API if Eircode is enabled

November 2022​

  • [API] Email Validation API now available
  • [Security] Wildcard subdomain allowed URLs available. Add *.domain.com to allow requests from domain.com and all related subdomains
  • [Address Finder] Search improvements: Better search for numeric property numbers with preceding zeros. Improved search for address ranges

October 2022​

  • [Security] Allowed URLs now permit subdomain wildcards. E.g. *.example.com will match example.com as well as all subdomains

August 2022​

  • [API] New Places API
  • [API] /places?query= to query for place suggestions
  • [API] Allow for IP, geolocation and country filtering and biasing
  • [API] places/:id to resolve details for a place given a suggestion

July 2022​

  • [API] /autocomplete/addresses/:id/gbr now returns the local format of an address if not located in GBR inside the native attribute
  • [API] /autocomplete/addresses/:id/usa now returns the local format of an address if not located in USA inside the native attribute

June 2022​

  • [Data] Irish Addresses (Eircode) now supported by the autocomplete API. Contact our support team to have this enabled on your account
  • [API] /addresses API now provides reverse geocoding if lon= and lat= query arguments are supplied. Results are ordered by proximity to the supplied geospatial points

May 2022​

  • [Data] UK Alias addresses now generally available
  • [API] /keys/:key API now returns a contexts which correlates with the user's locality

April 2022​

  • [Data] Welsh PAF addresses now generally available

March 2022​

  • [API] New autocomplete/addresses/:id/usa API which resolves address suggestions to the USA address format

February 2022​

  • [Data] Addressing data for USA available
  • [API] /autocomplete/addresses now accepts a context= argument which allows additional countries to be searched. This currently defaults to GBR but also accepts USA
  • [API] New autocomplete/addresses/:id/gbr API which resolves address suggestions to the GBR address format (regardless of country)

January 2022​

  • [API] The standard GBR address objects now also return an id attribute
  • [API] The standard GBR address object now also returns a dataset attribute which identifies the provenance of a result (e.g. paf means Postcode Address File, mr means Multiple Residence and nyb means Not Yet Built)
  • [API] The standard GBR address object now also returns a country_iso which returns the 3 letter ISO country code

December 2021​

  • [API] /addresses and /autocomplete/addresses now accept 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]
  • [API] /addresses and /autocomplete/addresses now accept query arguments to filter results by a geospatial box defined by "top-left" and "bottom-right" WGS84 coordinates. Filter addresses with box=[top left longitude],[top left latitude],[bottom right longitude],[bottom right latitude]

July 2021​

  • [API] /addresses and /autocomplete/addresses now accept 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]
  • [API] /addresses and /autocomplete/addresses now accept query arguments to filter results by a geospatial box defined by "top-left" and "bottom-right" WGS84 coordinates. Filter addresses with box=[top left longitude],[top left latitude],[bottom right longitude],[bottom right latitude]

June 2021​

  • [API] /addresses and /autocomplete/addresses now accept query arguments to bias results by locality or postcode elements like post_town or postcode_sector with bias_post_town= and bias_postcode_sector=

May 2021​

  • [API] /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)

April 2021​

  • [API] /postcodes/:postcode now returns total, limit and page attributes for all responses (not just Multiple Residence)

March 2021​

  • [API] /keys/:key API now accepts sublicensee keys that begin sl_

February 2021​

January 2021​

  • [Logging] Usage log exports now report the Origin header in the URL column if the Referer is not available

December 2020​

  • [API] 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

November 2020​

  • [Authentication] Licensee keys may now be passed in via the API Key argument of the querystring (api_key=) or authorization 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

October 2020​

  • [API] /addresses now accepts no terms query. This means addresses can be searched using just filters like postcode
  • [API] New filters available for /addresses including postcode_area, postcode_sector, uprn and more
  • [API] Search /addresses with UPRNs using the uprn= filter

September 2020​

  • [Data] Address responses now return a uprn attribute for GB addresses
  • [Data] GB address geolocations are now rooftop accurate if they have a uprn assigned