Enthuse and Bridgit: connect in one click

Built alongside Enthuse

We didn't build this integration after the fact. We worked closely with the Enthuse team while their new API was being shaped. That meant testing early versions, feeding back what we learned, and talking through how partners like Bridgit would connect.
The result is an API designed with integrations in mind from day one. Authentication uses modern, signed requests rather than long-lived shared secrets. And there is now a partner connection flow that hands credentials to Bridgit directly, so nobody has to handle them by hand.

Working with Maria and Craig

A big thank you to Maria and Craig at Enthuse. Working with them has been a fantastic experience from start to finish. They were open about where the API was heading, quick to answer questions, and genuinely interested in what would make life easier for the charities we both serve.
When we hit an edge case, we worked it through together. When we suggested a change, it was taken seriously. That kind of partnership is rare, and it shows in how smooth the connection is today.

Much easier for our shared clients

Connecting used to mean creating an API client in Enthuse, then copying an Org ID, a Client ID and a key file into Bridgit. It worked, but it was fiddly, and every copied credential was one more thing to get wrong or leave lying around.
Now it takes four steps:

1. In Enthuse, open Connections and click Connect on the Bridgit card.
2. Sign in to Bridgit, or create a free account.
3. Check the request and click Approve.
4. Your Enthuse connection appears in Your Connectors, ready to use as the source for a new bridge.

It's secure by design:

• Nothing connects until you approve it. You see exactly which organisation the connection is being added to.
• Server to server. Enthuse passes the credentials to Bridgit directly. They never pass through your browser or your clipboard.
• Single use and short lived. The link and the code behind each approval can only be used once and expire quickly.
• Verified live. Bridgit checks the credentials against Enthuse before the connection is saved.
• You stay in control. You can remove the connection at any time from your Connectors page.

Prefer to connect manually? That still works

The one-click flow is the easiest route, but it isn't the only one. If you'd rather manage your own API client in Enthuse, you can still connect the way you do today:
1. In Enthuse, go to Connections, choose Your own integration and create an API client.
2. In Bridgit, add a new Enthuse connection.
3. Copy across your Org ID, Client ID and JWK file.

Bridgit checks the credentials with Enthuse and the connection is ready to use, exactly as before. Both routes create the same kind of connection and work the same way in your bridges.

Get started

If you use Enthuse, look for Bridgit in your Enthuse integrations and click Connect. If you already connected manually, your existing connection keeps working. There's nothing you need to change.
Start building bridges. Secure, simple, ready in minutes.