Authenticate securely using OAuth 2.0 and API keys. Obtain client credentials from Accelevents, configure scopes, and store tokens securely in Rankr.
Rankr uses OAuth 2.0 to authorize access to Accelevents data. Tokens should be stored securely and refreshed automatically.
The integration uses endpoints to manage attendees, events, registrations, tickets, and payments. Use webhooks for real-time updates and configure token scopes to limit access.
Trigger: new or updated attendee in Accelevents
Actions: create or update the corresponding attendee in Rankr and link to events
Endpoint path: POST /attendees/sync
Key fields: attendee_id, email, event_id
Trigger: event created or updated in Accelevents
Actions: mirror event data to Rankr, push schedule updates
Endpoint path: PUT /events/{id}
Key fields: event_id, title, start_time
Trigger: payment processed in Accelevents or a new registration
Actions: record payment in Rankr and update registration status
Endpoint path: POST /registrations/{id}/payments
Key fields: registration_id, payment_id, amount
Automate data flow without writing code
Reduce manual data entry and human error
Trigger powerful automations in Rankr from Accelevents activity
This section covers common data elements, data flow processes, and how they relate across Accelevents and Rankr through OAuth tokens, API keys, endpoints, and synchronization workflows.
A clearly defined interface that lets software communicate with another system over HTTP.
A real-time notification sent by one app to another when an event occurs.
An authorization framework that enables apps to obtain limited access tokens securely.
A specific URL in an API that performs a function when called.
Use webhooks to push attendee changes to Rankr instantly and trigger automations.
Create events in Rankr when new Accelevents events are published.
Sync payments and registrations to ensure revenue data stays aligned.
Generate client ID and secret in Accelevents, then configure OAuth in Rankr.
Specify allowed endpoints and permission scopes for Rankr.
Run test syncs, monitor logs, and set up schedules.
The integration uses OAuth 2.0 with optional API keys. You will authenticate via client credentials; tokens expire and can be refreshed automatically. Store tokens securely and rotate them regularly to maintain access. If you’re using Rankr workflows, ensure your refresh tokens are wired into your automation to avoid downtime.
Available endpoints cover attendees, events, registrations, payments, and webhooks. Not every endpoint is required for every use case; select only those needed for your automation to reduce complexity and latency.
Yes. The Developer Marketplace templates allow many flows to be built without code. Basic scripting may be needed for advanced transformations, but most common integrations are achievable with no-code triggers and actions.
Token expiration can cause calls to fail. Use refresh tokens and automatic retry logic with exponential backoff. Monitor token expiry in the integration dashboard and re-authenticate when needed.
Yes. Field mappings let you align Rankr data with Accelevents fields for attendees, events, and registrations. You can map standard fields and custom fields to ensure data fidelity across systems.
Rate limits apply per API provider. Monitor usage in your dashboard, implement retries with backoff, and batch requests where possible to stay within limits.
Logs and history are available in the integration panel. You can view requests, responses, errors, and timing, and export data for audit or troubleshooting.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
