Choosing Your Localities Integration

Select the best way to integrate Woosmap Localities. This guide covers the REST API, the recommended Map JS API, and other client-side libraries.

  1. Choose Your Integration Path

This guide helps you choose the right integration path for your project. Find your use case in the summary table below or jump to a specific section for details.

Choose Your Integration Path

If you’re building… Use This For…
A backend or mobile app REST API Full, platform-agnostic control.
A location-aware web app Map JS API The recommended, unified map and search solution.
A simple web search bar JS Widget The fastest setup for non-map use cases.
A custom web UI JS SDK Complete UI control for non-map use cases.
A store locator Store Locator Widget Customizing the built-in search functionality.

1. REST API

For any non-browser environment, the REST API is your starting point. It provides direct, platform-agnostic access to the core Localities engine.

Go to the REST API Quickstart

This is the primary, forward-looking solution for building location-aware web applications. The Map JS API includes a powerful LocalitiesService that unifies both mapping and search into a single, seamless library.

See the Map JS API Guide

3. Other Web Integrations

For web use cases that do not involve a map, these standalone libraries are excellent choices.

4. Customizing the Store Locator

If you’re using the Store Locator Widget, you can customize its built-in Localities search to switch from geocoding to interactive autocomplete and filter the results.

See the Store Locator Integration Guide

Was this article helpful?
Have more questions? Submit a request