INTEGRATION GUIDE
EvenUp Integration
Connect your Smokeball matters to EvenUp so cases, defendants, and documents stay in sync automatically.
The EvenUp integration connects your Smokeball matters to your EvenUp workspace. Once it's live, matters you create in Smokeball automatically appear as cases in EvenUp — along with their defendants and documents — and stay up to date as you work. There's nothing to re-key by hand.
This article covers connecting your Smokeball account to EvenUp and what happens after you do. For questions about EvenUp itself — how cases are structured, demand packages, billing, or anything you see inside the EvenUp product — visit EvenUp's support site.
|
INTEGRATION OWNER This integration is built, owned, and supported by EvenUp. Smokeball provides the API access that makes it possible, but EvenUp is responsible for the integration's setup, configuration, and ongoing support. Please direct integration issues to EvenUp. |
Before you start
You'll need all three of the following:
✓ An active Smokeball account with permission to authorize third-party applications on behalf of your firm. If you're not sure whether you have this, check with your firm's Smokeball administrator.
✓ An active EvenUp account for the workspace your matters should sync into.
✓ An integration request submitted to EvenUp. This integration isn't self-serve — EvenUp's integration engineers configure it for your firm before it goes live. Contact EvenUp to start the process. They'll confirm which matters should sync and how your Smokeball fields map into EvenUp before sending you the connection links below.
This integration is currently available to firms on US-hosted Smokeball accounts only.
Connect your Smokeball account
You'll authorize EvenUp twice — once for your sandbox environment and once for production. Both are required. EvenUp cannot complete your setup until it has both.
| 1 | Sign in to Smokeball in your browser, so the authorization prompts recognize you. |
| 2 | Click Connect Sandbox below. Smokeball's sign-in page opens. |
| 3 | Sign in and approve the access request. |
| 4 | You'll land on a blank page showing 200: success. That's the confirmation the authorization went through — there's no further screen to click. Note the page down and close the tab. |
| 5 | Return here and click Connect Production. |
| 6 | Sign in and approve the access request again. |
| 7 | Confirm you see 200: success a second time. |
Â
Both links open Smokeball's secure sign-in page.
|
WHAT HAPPENS NEXT Authorizing does not turn the integration on. It gives EvenUp the credentials they need to finish building your integration on their side — connecting your matters to the right EvenUp workspace, applying your firm's sync rules, and testing. You won't see matters flowing into EvenUp right away. EvenUp's integration engineers will confirm with you when the integration is live. |
Â
|
IF YOU DON'T SEE 200: SUCCESS An error page, or a redirect somewhere unexpected, means the authorization didn't complete. Try again in a private/incognito window, and if it still fails, send EvenUp a screenshot of what you did see. |
What syncs, and how often
The integration is one-directional: information flows from Smokeball into EvenUp. Nothing you do in EvenUp is written back to your Smokeball matters, so your Smokeball data is never modified by the integration.
Sync is event-driven and near-real-time. Rather than checking on a schedule, Smokeball notifies EvenUp the moment something changes, so updates typically appear in EvenUp within moments of the change in Smokeball.
| When this happens in Smokeball | This happens in EvenUp | Timing |
| You create a matter | A matching case is created | Near-real-time |
| The matter has one or more defendants | Those defendants are added to the EvenUp case | With case creation |
| You add or update a document on a matter | The document is uploaded to the matching EvenUp case | Near-real-time |
| You close a matter | The EvenUp case status is updated to reflect the closure | Near-real-time |
Â
A few details worth knowing:
✓ Documents sync incrementally. Only files that are new or changed since the last sync are sent, so a document is never uploaded twice and existing files aren't re-sent every time you touch a matter.
✓ Documents only sync for matters that already synced. If a matter never created an EvenUp case — because it fell outside your firm's sync rules, for example — its documents won't sync either.
✓ Defendants sync only when the matter has them. Matters with no defendants recorded simply create the case.
✓ Not every matter has to sync. EvenUp can limit sync to specific matter types, subtypes, categories, or statuses, so only the matters that belong in EvenUp are sent. Your firm's rules are agreed with EvenUp during setup — ask them if you're unsure what's currently in scope.
✓ Existing matters can be backfilled. As a one-time step during onboarding, EvenUp can import your existing open matters and their documents into EvenUp so both systems start aligned. Ongoing sync then picks up from there.
Disconnecting the integration
|
HOW TO DISCONNECT Contact EvenUp to disconnect. Because EvenUp owns and operates this integration, deauthorization is handled on their side — reach out to EvenUp support and ask them to remove your firm's Smokeball connection. |
Â
EvenUp will remove the connection and stop the event subscriptions, after which no further matters, documents, or status changes will flow from Smokeball to EvenUp.
Cases and documents already synced into EvenUp remain in your EvenUp workspace after disconnecting. If you want those removed as well, tell EvenUp when you make the request — deletion in EvenUp is handled separately from turning off the sync.
Â
| Â | Need help with the integration? Contact EvenUp. For EvenUp product questions, see evenuplaw.com/support. |
Â