Connect RemyPass to the tools your team already uses
API-first, built for your stack
Use native connections, secure API access, and event-driven webhooks to keep RemyPass aligned with the systems that remain important to your organisation.
Create one joined-up operational flow
RemyPass can act as the membership and credential layer while data moves deliberately between your CRM, payments, ecommerce, forms, and reporting stack.
- Native integrations for common platforms
- REST API access for custom workflows
- Webhooks for timely event-driven updates
Remove the friction around integrations & api
- Teams copying data between core business systems
- Nightly exports leaving access information out of date
- Rigid platforms blocking organisation-specific workflows
How it works with RemyPass
- Map the systems and source of truth for each data type
- Choose a native integration or build with the API and webhooks
- Monitor the connected workflow and expand it as requirements grow
What your team can achieve
- Less duplicate data entry
- More current information across systems
- A platform that adapts to your operation
Questions about integrations & api
Which native integrations are available?
RemyPass currently supports focused integrations with Stripe, Blackbaud, Square, Mailchimp, and Shopify. Each integration handles a defined workflow rather than attempting to copy every record between both platforms.
What can we do through the API?
The public API supports reading, creating, and updating members; reading pass templates and issued passes; issuing membership cards and event tickets; and managing pass expiry, revocation, reinstatement, and email delivery.
Can we use our custom member fields through the API?
Yes. Member creation and update workflows can include organisation-defined custom fields.
Can one API key access everything?
Only if it is deliberately given the relevant scopes. Separate keys can be created for different integrations, with each key limited to the member or pass actions it requires.
Can API keys expire or be revoked?
Yes. Keys can have an expiry date and can be deactivated or deleted from RemyPass.
Can we monitor API usage?
Yes. Administrators can review request volume, successes, failures, response times, recent requests, and when each key was last used.
Which webhook events are available?
Customer-configured outbound webhooks currently notify connected systems when a scan is recorded. The payload includes the member, location, result, reason, and timestamp.
How are webhooks secured?
Webhook payloads are signed using HMAC-SHA256. RemyPass also requires HTTPS endpoints and provides a unique delivery ID with each request.
What happens if our webhook endpoint is unavailable?
RemyPass retries unsuccessful deliveries using configurable retry settings and exponential backoff. Repeatedly failing subscriptions can be disabled automatically.
Can RemyPass keep Blackbaud membership cards current?
Yes. Supported Blackbaud integrations can create members, issue passes, update expiry, and change member and pass status as the source membership changes.
Is Mailchimp synchronisation two-way?
No. RemyPass adds or updates eligible members in one selected Mailchimp audience. It does not import Mailchimp subscribers into RemyPass.
Can Shopify automatically recognise active members?
Yes. RemyPass can maintain an active-member customer tag and segment in Shopify, which can be used with a Shopify automatic discount.