Find the endpoint in DevTools
Chrome, Edge, Firefox and Safari all have the same panel under slightly different names. These steps use Chrome's.
- Open the page with the store locator and press F12 (or Cmd+Option+I on a Mac) to open DevTools.
- Choose the Network tab and click the Fetch/XHR filter, so only background data requests are listed.
- Click the clear button, then run a search in the locator: type a town and press enter.
- Watch new rows appear. Click each and open the Response or Preview tab. The one you want returns a list with names, addresses, and latitude and longitude.
- Open the Headers tab of that request to read its URL and parameters, often something like lat, lng, radius, limit or a site or account id.
- Right-click the request and choose Copy, then Copy as cURL, to repeat it from a terminal while you work out what each parameter does.
Patterns you will see
Some locators batch everything into one large request; others page through results. Both are normal.
| What you see | What it usually means |
|---|---|
| One request on page load returning every location | The locator filters in the browser; the endpoint has no search parameters |
| A request per search with lat and lng | Server-side proximity search; radius and limit control the result size |
| A geocoding request before the search | The town you typed is turned into coordinates by Google or Mapbox first |
| A key or token in the URL | A public, domain-restricted key; it is meant for the browser, not for reuse elsewhere |
| Nothing in Fetch/XHR, results still appear | The data is embedded in the page HTML or a script file; check the Doc and JS filters |
Before you use an endpoint you found
The rest of this guide is about the opposite case: a locator you own, where you should never have to reverse-engineer anything.
- Read the site's terms of use. Many forbid automated collection, and an endpoint being reachable does not change that.
- Check robots.txt for the path, as a signal of the owner's wishes.
- Expect it to change. Undocumented endpoints have no contract; a redesign can break your integration overnight.
- Respect rate limits. Space requests out, cache what you get, and stop if you see 429 responses.
- If you need the data regularly, ask the owner. Many brands will send a feed or a CSV to a retailer or partner who asks.
On a Handled-powered page
If you open DevTools on a page running Handled Locator, you will see the widget request its locations from a public endpoint scoped to that site's id. It returns only locations the owner has marked visible, and it exists to serve the widget, so its shape can change with the widget.
For anything you build yourself, use the documented interfaces below. They are versioned, scoped by key, and described in the Location API docs.
Handled's documented interfaces
Each of these has a stable, documented contract, unlike an endpoint found in DevTools.
| Interface | What it does | Plans |
|---|---|---|
| REST Location API | List, read, create, update and archive locations at /api/v1/locations, with a bearer key that can be read-only | Pro and Business |
| Query API | Nearest-first results near a point or matching a tag or text, at /api/v1/query, ranked as the widget ranks them | Pro and Business |
| Webhooks | Signed calls to your URL when a location is created, updated or deleted, or a lead arrives, retried for two days | Pro and Business |
| Widget JavaScript API | Methods on the embedded element: search, searchNear, setFilters, openLocation, getLocations and more | Every plan |
| Widget events | Browser events for ready, search, no results, selection, directions and action clicks | Every plan |
| MCP server | 28 tools for ChatGPT, Claude and other MCP clients to read and change locations and design | Every plan, including the trial |
Which one to use
Rate limits on the REST APIs are 120 reads and 30 writes a minute per key. Keys are created by the account owner and shown once. The developer hub has every surface in one place, and MCP server docs list all 28 tools.
- Build your own store-finder page or a mobile app: the Query API with a read-only key.
- Keep the locator in step with a system you own: the Location API to write, webhooks to hear about changes.
- Drive the embedded locator from your own page, such as a find-near-me button on a product page: the JavaScript API.
- Send locator activity to analytics: widget events.
- Ask for changes in plain words, or let an assistant answer questions about your locations: the MCP server, in ChatGPT or Claude.
Frequently asked questions
How do I find a store locator's API?
Open DevTools, go to Network, filter to Fetch/XHR, run a search in the locator, and look for the response containing names, addresses and coordinates. Its Headers tab shows the URL and parameters.
Can I use a store locator endpoint I found in DevTools?
Check the site's terms first. Undocumented endpoints are not a contract, can change without notice, and may be off-limits for automated use. Ask the owner for a feed if you need the data regularly.
Does Handled Locator have an API?
Yes. A REST Location API, a Query API and webhooks on Pro and Business, a JavaScript API and browser events on every plan, and an MCP server for ChatGPT and Claude on every plan.
Can ChatGPT read my store locations?
With Handled, yes. Install the Handled Locator plugin in ChatGPT and sign in; it can list, find nearest, add and update locations, and propose design changes for you to confirm.