Authenticate requests using the saas/location.read scope. Include your API key in the Authorization header when calling endpoints.
Configure a secure connection in Manychat using OAuth or a dedicated app token and map credentials in the integration settings.
Endpoint 1: GET /locations pulls location data for chat flows. Endpoint 2-17 are not required for this page but available for extended use.
Trigger when a location is created or updated in Snapshots API
Actions: update contact attributes in Manychat, enroll in a campaign, or send a targeted message
GET /locations
location_id, name, region, status
Trigger: location data changes that affect segments
Actions: add or remove users from segments, trigger flows
GET /locations
location_id, region, tags
Trigger: location status changes that require a notification
Actions: notify users, update CRM fields, or push alerts
GET /locations
location_id, status, last_updated
No coding required to sync location data into chat flows
No code automation through configurable triggers and actions
Scalable messaging across campaigns without writing code
Key elements include endpoints, triggers, actions and data mapping; processes cover authentication, mapping, testing and deployment
Application Programming Interface, a set of rules for accessing data between systems
A specific URL path for an API operation
A callback URL that notifies your app of events
An authorization framework that grants token based access
Send location tailored welcome messages when a user shares their location in chat
Route users to flows based on their location data
Automatically notify teams on location changes
Generate an API key in Snapshots API, configure in Manychat, and set the saas/location.read scope.
Set GET /locations as the source, map location fields to user attributes
Test end to end in a test chat, then roll out to production
Not necessarily. You can connect using built in connectors and webhooks without writing code. The Snapshots API can be called from Manychat using a simple API key and mapped fields. In many cases a no code setup is sufficient to drive location based messaging. If you need more complex logic, you can extend with custom HTTP requests or middleware between systems. Remember to include the saas/location.read scope for read access to location data.
You can sync location identifiers, names, regions, statuses and related tags. This data can populate user attributes in Manychat and trigger messages or sequences. Additional fields can be brought in as custom attributes as needed. In practice map endpoint response fields to the user profile in Manychat for personalized flows.
The required permission is saas/location.read to read location data. Ensure your API key or OAuth scope includes this. If you need write access, request appropriate scopes from your API administrator.
Authentication typically uses an API key with the Authorization header and the saas/location.read scope. In Manychat you configure the key in the integration settings. Rotate keys regularly and store tokens securely.
Yes. You can map custom fields by creating corresponding user attributes in Manychat and linking them to fields returned from GET /locations. This enables dynamic personalization in chat flows. Two way mapping can be set up with additional endpoints if needed.
Rate limits depend on your plan and the API. Implement simple retry logic and exponential backoff to handle spikes. If you anticipate high volume, consider batching requests or using webhooks where available.
Endpoint details are documented in your Snapshots API docs. For this page the primary endpoint shown is GET /locations. Additional endpoints can be indicated in the API reference and used as needed for advanced scenarios.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
