Authenticate requests with your Snapshots API access token. Include an Authorization header like Bearer
Connect using OAuth 2.0 via Zapier’s connector, or use an API key if your workflow requires it. Zapier will manage token refreshing and secure storage.
Endpoint1: GET /locations — Retrieve a list of locations accessible with the saas/location.read scope. Endpoint2-54: Refer to the Snapshots API documentation for the full list of endpoints and their usage.
Trigger: When a new location is created or an existing location is updated in Snapshots API.
Action: Retrieve location data with GET /locations and map fields into Zapier Tables for immediate downstream use.
GET /locations
id, name, latitude, longitude, status, last_updated
Trigger: Scheduled sync (e.g., every 15 minutes) to pull the latest locations.
Action: Use GET /locations to fetch records and append/merge into Zapier Tables for dashboards.
GET /locations
id, name, last_updated
Trigger: On-demand or filter-based pull via Zapier UI.
Action: Call GET /locations with query parameters to filter results, then push into Zapier Tables.
GET /locations
id, name, status
Low-code automation: Build workflows quickly without writing code.
Faster data syncing: Real-time or scheduled updates keep your tables up-to-date.
Scalable integrations: Add more endpoints and fields as your data needs grow.
This glossary explains the core terms used when integrating Snapshots API with Zapier Tables, including endpoints, authentication, and data mapping.
A specific URL and HTTP method used to access a resource in an API.
Numerical codes returned by the API to indicate success, failure, or errors (e.g., 200, 401, 404, 429).
The process of verifying identity and granting access using tokens, keys, or OAuth 2.0.
Maximum number of requests allowed within a time window to prevent abuse.
Pull the latest locations once a day and summarize changes in a Zapier Table or email digest.
Set up a Zapier workflow to notify teams when a location changes status or goes offline.
Export location history to CSV or a data warehouse for analytics.
Open the Zapier Tables connector for Snapshots API and start an OAuth 2.0 or API key-based connection.
Choose GET /locations as the trigger, then define filters and polling frequency.
Map API response fields to Zapier Tables fields and run a test to verify data flow.
Yes. You’ll need appropriate API credentials for the Snapshots API. Use them in your Zapier Tables connection to authorize requests. Make sure the credentials include the saas/location.read scope for read access. If you encounter permission errors, verify that the token is active and has the required scope assigned. Additionally, ensure you’re connecting to the correct environment (sandbox vs. production) and that your account has the necessary permissions to access location data.
The saas/location.read scope allows read-only access to location data. It is designed to protect sensitive information while enabling you to pull location data into Zapier Tables. If your workflow requires additional actions, you may need higher-level scopes or separate endpoints, depending on your API plan and the available permissions. Always follow the principle of least privilege.
GET /locations returns current location data. Historical data may be accessible via subsequent requests if the API supports a history or last_updated parameter. If historical endpoints exist, they will be documented in the Snapshots API reference. For full history, you may need to paginate through records and store them in Zapier Tables over time.
Sync frequency is configurable in Zapier Tables—common options include every 5, 15, or 60 minutes, or on-demand. Real-time near-instant updates depend on the API’s webhook or poll-based design. Be mindful of rate limits and set polling to a sustainable interval for your plan.
Yes. In addition to GET /locations, you can typically access other endpoints listed in the Snapshots API documentation. If some endpoints are restricted by your plan or require elevated permissions, upgrade rights or obtain additional API access from your account administrator. Always consult the official docs for endpoint availability.
If you hit a rate limit, the API will return a 429 status. Implement backoff in your Zapier workflow and retry after the configured window. The rate limit details (per minute/hour) are provided in the API documentation and may vary by plan.
To test your connection, run a manual fetch of GET /locations from the Zapier Tables connector, verify that fields map correctly, and review the API response. Use test data in Zapier’s test mode and check for proper authentication, correct scope, and successful data mapping.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
