Instance · Locator
Locator Overview
Last updated 1 November 2026
The data behind a store finder: locations, categories, enquiries and their fields.
The Locator holds the data behind a store or branch finder: your locations, the categories that group them, and the enquiries visitors send about them. Your developers use this data to build the map and search on your website. It suits any business with physical places, such as restaurants, clinics or schools.
What is in the Locator
| Area | What it holds |
|---|---|
| Locations | Places, with address, map position, opening hours, contacts, media and FAQs |
| Categories | Groups of locations that visitors filter by |
| Enquiries | Messages sent about a location |
| Custom fields | Your own fields on locations |
| System fields | Ten dropdown slots you can rename and fill with options |
Google Maps
The address field on a location suggests addresses as you type. It uses the Google Maps key set in the CRM integrations, so set that key first.
From code
The Locator API at /locator/api/v2/ covers categories, locations, enquiries and system fields, with full create, read, update and delete, and can list and delete custom-field definitions. Updates use PUT. FAQs, imports, exports and saved filters are in the admin only.
curl -H 'Authorization: instance_YOUR_KEY' 'https://your-instance/locator/api/v2/locations?page=1&per_page=10'The docs.insites.io instance has no locations, so no response is shown.
Each location can also hold FAQs, images, opening hours for every day of the week, and its own search and sharing settings.
Common mistakes
- Building your own locations table. The Locator already has one, with admin screens and an API.
- Using PATCH for updates. The Locator uses PUT.
- Defining custom fields through the API. Definitions are made in the admin; the API only writes values.