Authenticate requests using your Snapshots API key and recommended OAuth flow to keep data secure while syncing to Accelevents.
Ensure Accelevents can authorize the Snapshots API connection with proper scopes and permission grants for location and event data.
– GET /locations (Locations data) – Other endpoints available upon request
Trigger: When venue or location data changes in Accelevents.
Actions: pull location records, map fields (id, name, address, city, country, timezone), and push updates to Accelevents.
GET /locations
Key fields: id, name, address, city, country, timezone
Trigger: New registrations or attendee updates in Snapshots API.
Actions: create/update attendees in Accelevents, synchronize event and enrollment data.
GET /events
Key fields: event_id, attendee_id, status, registered_at
Trigger: Updates in Snapshots API occur (e.g., status changes, new records).
Actions: deliver webhook payloads to Accelevents to trigger workflows and keep data synchronized.
POST /webhooks/receivers
Key fields: event_type, payload_id, timestamp
Automate data flow without writing code and reduce manual data entry.
Keep teams aligned with real-time data across locations and events.
Scale integrations with simple configuration and outgoing endpoints.
Explore API basics: endpoints, authentication, data mapping, webhooks, and error handling that power Snapshots API integrations with Accelevents.
A set of rules that lets apps talk to each other and exchange data.
A specific URL on an API that performs an action or returns data.
The process of verifying identity and granting access to resources.
A callback URL that receives real-time data updates from an API.
Automatically pull location data to manage venues in Accelevents with real-time updates.
Synchronize attendee and session data to keep dashboards current.
Build cross-system dashboards showing location and attendance metrics.
Request your Snapshots API key and configure scopes for location.read access.
Enter the API key and endpoint details in the Accelevents connector and authorize.
Run test data syncs, review logs, adjust mappings, and go live.
Snapshots API connections use API keys and OAuth to secure data and control access. Always use HTTPS and limit scopes to saas/location.read to minimize exposure. If you encounter authentication errors, verify the API key, confirm the app has the correct scopes, and ensure any IP whitelisting requirements are met. For ongoing security, rotate keys periodically and monitor usage for anomalies referenced in the Accelevents integration logs.
Current documentation highlights the Locations endpoint (GET /locations) as a core data source for venues. Additional endpoints are available as your integration needs grow and can be enabled upon request. Review the API reference for endpoint-specific parameters and response schemas. If you don’t see an endpoint you need, you can request access or a custom mapping guide from Rankr support to extend your integration.
No heavy coding is required. The integration is designed to be configured in the Snapshots API connector within Accelevents or via Zapier-style workflows. Basic mapping of fields suffices for most common use cases, with advanced mappings possible through custom fields and webhooks. If you are a developer, you can still customize field mappings and event triggers to fit complex workflows.
Test data synchronization by performing a dry run in the connector, then examine logs for each endpoint (locations, events, attendees). Validate data mappings, timestamps, and error messages. Resolve any mismatches and repeat until the test pass is confirmed. Enable verbose logging during the test phase to capture payloads and mapping results for easier troubleshooting.
Common mappings include id, name, address, city, country, and timezone for locations; event_id, attendee_id, status, and registered_at for attendees; plus metadata for events and sessions. Use consistent data types and ensure date formats align across systems. Document any custom fields you introduce to prevent downstream mismatches and to simplify future maintenance.
Authentication issues are usually due to expired keys, incorrect scopes, or misconfigured redirect URLs. Re-check the API key, re-authorize with the correct scopes, and confirm the connector uses HTTPS. If problems persist, inspect the integration logs and reach out to support with your key ID and error codes.
API keys are provided from the Snapshots API dashboard. The documentation is available on Rankr’s developer portal and within the Accelevents integration guides. If you need additional endpoints or detailed field mappings, contact Rankr support to obtain the latest docs and configuration examples.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
