Authenticate requests with your Snapshots API credentials from GHL. Use your token and include the saas location read scope in API calls.
Authorize 123FormBuilder to access Snapshots API data. You will be prompted to grant permissions during setup.
GET /locations is the primary endpoint used to retrieve location data
Trigger when new location data is available from Snapshots API
Map location fields to 123FormBuilder form fields and create or update entries
GET /locations
location_id, name, address, coordinates
Triggered queries with filters to fetch specific locations
Populate filtered results into 123FormBuilder fields
GET /locations?filter=
location_id, region, status
Location updates trigger alerts or form updates
Push updates to 123FormBuilder forms or dashboards
GET /locations
location_id, updated_at
Automate data entry and updates without writing code
Keep forms in sync with real time location data
Scale to manage multiple locations across teams
A quick glossary of terms and how data flows between Snapshots API and 123FormBuilder
An interface that lets Snapshots API and 123FormBuilder exchange data
Process of validating identity to access the API and grant permissions
A specific URL where a particular API function is available
A secure string used to authenticate API requests
Auto fill forms with live location data to speed data capture
Set up approval workflows when a location meets criteria
Display location summaries in forms and dashboards
In GHL generate an API key or OAuth token for Snapshots API
Authorize 123FormBuilder to access Snapshots API with saas/location.read
Map location fields to form fields and run a test
The Snapshots API integration with 123FormBuilder lets you pull location data into forms and workflows without code. It connects your GHL account to the Snapshots API so you can automate data capture. The setup uses the saas location.read scope to access location information.
No coding is required. Use the connector to map endpoints to form fields and set up triggers. Follow the steps to generate credentials and authorize the connection, then test the data flow.
The /locations endpoint returns location identifiers, names, addresses, and coordinates. Depending on your configuration you may also receive status or region data.
Authenticate with your GHL credentials and include the access token in requests. Use OAuth or an API key as provided by your GHL developer console and ensure the saas/location.read scope is granted.
The required scope saas/location.read ensures read access to location data. Your connection will operate within this scope to retrieve location details.
Yes, you can add filters to your /locations requests to fetch specific locations. Use query parameters to narrow results by region or status.
If you see errors, check credential validity, ensure the correct scope is granted, and verify endpoint paths and field mappings. Consult logs and test calls to diagnose issues.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
