What’s new in v6?

• Secondary address support allows for retrieving apartment units and business suites via forward geocoding, including those with coordinates unique from their parent address.
• Structured Input allows queries to be separated into component parts for greater accuracy.
• Smart Address Match makes the match_code object available in all responses for address–type features, and indicates how well a result corresponds to the submitted query.
• Improved Batch geocoding sends up to 1000 queries of mixed-type in a single request. API rate limits still apply and each query will be counted as 1 request.
• Expanded Japan coverage gives access to robust Japanese address search.

Migrating from Geocoding v5

• Permanent and temporary geocoding are no longer different endpoints, and are now set via an optional parameter. The default behavior for all endpoints is temporary geocoding.
• Forward and reverse geocoding now have their own separate endpoints.
• Batch geocoding now has it’s own endpoint.
• The Geocoding v6 API no longer provides POI data (use the Search Box API for POI search).
• Streets can now be returned as a feature type and be filtered for via the types parameter.

Geocoding from Snowflake

Snowflake users can do batch geocoding operations on data stored in their data warehouse. The Mapbox Snowflake Native App is available in the Snowflake Marketplace.

For more background information on the Mapbox Geocoding API and how it works, see the How geocoding works guide.

You may also use one of several wrapper libraries to integrate the Mapbox Geocoding API into an application instead of using it directly.

• For Mapbox Search JS SDK, Geocoding components are available on releases 1.0.0-beta.20 and later.