# Integrations | Kodex in the Systems You Already Run

Source: https://www.kodexglobal.com/integrations

> Kodex plugs into the systems your team already runs. Route law enforcement data requests into your project management, ticketing, and case tools.

Integrations

## We plug into the systems
you already run

Real APIs and maintained integrations for the tools your team already works in.

Request a demoSee how integrations works

### The legal and engineering teams at the world’s largest crypto exchanges, banks, and telcos integrate Kodex into the systems they already run.

Trusted by

Outcomes

97.5% Fewer law enforcement tickets Coinbase case study → 99.9% Faster law enforcement verification Bitget case study → 99% Of legal request issues resolved Bitfinex case study →

APIs

### Most “integrations” in this
category are a CSV export.
Ours aren’t.

#### Verify any requester from your own systems.

The Verification API returns a verified-or-not result on any law enforcement requester your systems encounter. Drop it into your intake flow, your case opener, or your support escalation path: anywhere knowing the requester is real changes what your team does next.

Your systems
Intake flow Case opener Support escalation
Verification API
County sheriff’s office
Agency confirmed Verified

Unverified sender
Not verifiedBlocked

#### Produce data without an engineer in the loop.

The Data Production API automates the work of producing data on a request. Account lookups return automatically from your backend. Drafts get reviewed before they leave your environment. The data your team produces stays under your control until you decide to deliver it.

Data Production API
Your environment

Account lookup · KX-24471 Returned from your backend

Draft response In review

Delivery Held until you deliver

#### Put the network on your own front door.

Sign in with Kodex puts the network’s verification engine behind a single button on your own legal center. The same engine that powers the rest of Kodex, deployed into your portal instead of ours.

Your legal center legal.company.com Sign in with Kodex

356 Verified 28 Blocked

Your stack

### Where we connect
with the rest of
your stack.

Jira

#### For enterprises that run legal work in Jira.

Verified requests route directly into your Jira workflows. Fulfillment happens in the tool your team already runs. Status syncs back automatically.

Kodex → Jira
01Route requests

02Review & assign

03Fulfill & sync

Hummingbird

#### Compliance teams on Hummingbird.

Kodex request and response activity syncs into Hummingbird for compliance teams running on that platform.

Kodex → Hummingbird
01Capture activity

02Record compliance

03Generate audit trail

Custom

#### For everything else, built to order.

Scoped integrations into internal case management, ticketing, and workflow systems via the underlying APIs. The team that builds them is the team that built Kodex.

Kodex → Your systems
01Scope integration

02Config APIs

03Deploy integration

FAQ

### Questions teams
ask before they
integrate.
Request a demo

How is this different from what other platforms call an “integration”?

Most of what gets called an integration in this category is a CSV export. Ours are real APIs and bidirectional connections to named systems. The Verification API and Data Production API are programmatic surfaces engineering teams can build on. Jira and Hummingbird sync both ways. CSV exports don’t make this list.

Do we have to use all three APIs to get value?

No. The Verification API, Data Production API, and Sign in with Kodex are independent. Use one, use all three, or start with one and add the others later.

What if the system we use isn’t on your integrations list?

Jira and Hummingbird are the named integrations we build and maintain. For anything else, the Kodex team builds scoped custom integrations on top of the same APIs. The same team that built the network builds the integration.

Where does the data live during an integration?

In your environment. The data your team produces stays under your control until you decide to deliver it. Kodex sees what your systems return at the moment of delivery, not before.

Do we need to be a Kodex customer to use the integrations?

Yes. The APIs are the same surface the Kodex application runs on, and so is Sign in with Kodex. The integrations bring the network into your systems. They don’t bypass it.