Start by generating an API key, selecting the saas/location.read scope, and securely storing credentials to authorize requests from Motion.
Grant Motion the necessary permissions to access Snapshots API endpoints, then configure token rotation and scope scope constraints.
1) GET /locations — Retrieve location data. (Other endpoints will be documented as you enable more features.)
Trigger: a location update in Motion automatically pushes the change to Snapshots API in real time.
Actions: upsert location records in Snapshots API to keep both systems in sync.
GET /locations
Key fields: location_id, name, status, last_updated
Trigger: a batch sync runs every 15 minutes to refresh data.
Actions: batch upsert of multiple location records in Snapshots API.
POST /locations/batch
Trigger: webhook or manual lookup to fetch the latest locations.
Actions: fetch and store fresh location data for reporting.
GET /locations/{id}
Fields: id, name, coordinates, last_updated
Automate data flow without writing a line of code—set up triggers and actions in minutes.
Reduce manual data entry and human error with reliable sync.
Gain real-time visibility into your locations for faster decisions.
Learn the core elements and processes that make the Snapshots API and Motion integration smooth and understandable.
A programmable interface that lets systems communicate and exchange data.
A mechanism that delivers real-time data to a configured URL when events occur.
The process of verifying identity and granting access to APIs and endpoints.
A URL that represents a resource for a specific API operation.
Generate scheduled, shareable reports from your location data in Snapshots API.
Send instant alerts when a location changes status or value.
Create a lightweight portal to search and view locations from both systems.
Generate or retrieve your API key and secret, then store securely.
Set up webhook endpoints in Motion to receive updates from Snapshots API.
Run test requests and verify data integrity and timeliness.
To get started, generate an API key from the Snapshots API dashboard and grant Motion access with the saas/location.read scope. Then configure your app to use that key for authenticated requests. Ensure you securely store credentials and rotate them periodically.
Use API keys or OAuth depending on your security requirements. For Motion, a long-lived API key with proper scopes is recommended, plus client-side secret storage and secure server-side calls.
At first, only GET /locations is available. As you enable more features, additional endpoints will appear in your docs.
Respect rate limits, implement exponential backoff, and handle common HTTP errors with clear retry logic. Test thoroughly in a staging environment.
Yes. Use sandbox/test environments or development keys to validate behavior without affecting production data.
Batch processing and webhooks are supported. You can configure batch endpoints and webhook listeners in Motion.
API docs can be found in the Snapshots API developer portal and the Motion integration guide.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
