# The Kodex API | Automate Law Enforcement Data Requests Source: https://www.kodexglobal.com/api > The Kodex network, accessible by API. Receive, verify, and respond to law enforcement data requests from your own systems and workflows. Kodex API ## Build on our network. Some teams want the Kodex application. Others have already built their own. The Kodex API gives you programmatic access to the same network, verification engine, and data production workflow the application runs on. Build what you want on top of it. Request a demo ### Trusted by 15K+ government agencies and the world’s leading crypto, financial services, and telecom companies. 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 → One surface ### Three APIs. One network. The Kodex API is one surface: the Verification API, the Targets API, and status webhooks. Same authentication, same network, same intelligence layer. Only the endpoint changes. #### Verification API Pass in a requester. Get back a verified-or-not result, with the metadata your systems need to act on it. Drop it into your intake flow, your case opener, or your account access path: anywhere the trustworthiness of the counterparty changes what your team does. The same verification engine that gates the Kodex portal, exposed for your own systems. POST /v1/verification/lookup - Requester - 200 OK - Verified Verification API { "email" : "agent.smith@fbi.gov" , } { "status" : "ACTIVE" , "substatus" : "VERIFIED" , "agency" : "FBI Cyber Division" , "jurisdiction" : "US-Federal" , "verified_at" : "2024-08-14T19:22:00Z" , "last_active" : "2026-05-20T11:08:00Z" } #### Targets API Automate the work of producing data on a verified request. Account lookups return programmatically from your backend. Drafts surface for review before they leave your environment. The data your team produces stays in your environment until you decide to deliver it. GET /v1/requests/{request_id}/targets - Validated Request - Pull the data from kodex - Returns the targets data Targets API { "request_id" : "req_3f8a..." , "targets" : [ { "type" : "email" , "value" : "user@example.com" , "validated" : true , "source" : "auto_extracted" }, { "type" : "client_uid" , "value" : "user-e9BZSuaGgK5nwjLMCm89JEg3" , "validated" : true , "validation_rule" : "openai_user_id" } ] } #### Status webhooks Get notified the moment an agent’s credentials change. POST {your_webhook_url} - Agent account changes - Kodex detects problem - Kodex sends webhook to your server Status webhooks { "email" : "agent.smith@fbi.gov" , } { "event" : "agent.suspended" , "agent_id" : "agt_8a2f4b1c" , "previous_status" : "ACTIVE" , "current_status" : "SUSPENDED" , "reason" : "credential_compromised" , "timestamp" : "2026-05-21T14:32:00Z" } Patterns ### What you can build A few of the patterns customers run on the API today. #### Smarter legal intake Verify the requester behind every inbound legal request before a case is ever opened. #### Native integration Embed Kodex verification inside your own product, so your customers benefit from the network without ever leaving your surface. #### Engineer-free workflows Pull the data behind a verified request directly from your systems of record, with no engineer in the loop. #### Secure draft routing Route drafts through your existing review workflow before anything leaves your environment. #### Complete audit trails Stream every verification, every production, every delivery into your SIEM and audit pipeline. Teams ### When the API is the right choice. Enterprise legal teams #### Large enterprises with their own legal centre. You have the workflow, systems of record, and review process. The API brings the network’s verification and data production into them. Kodex is the trust layer underneath. Your product Verification API Verified Verification API beneath your product Platform & SaaS companies #### Platform companies whose customers also handle requests. Embed Kodex’s verification engine into your own product so your customers benefit from it. The Verification API is what powers that motion. Verified request Email Status agent@leo.gov 2 risk signals detected Suspended agent@agency.gov Verified sus@leo.gov 1 risk signal detected Pending admin@agency.gov No account Infrastructure-minded teams. #### Built for teams that think in systems. For teams that treat lawful data access the way a CISO treats identity, Kodex isn’t an application. It’s infrastructure, and the API is how you consume it. 01Verification API 02Data protection API 03Kodex Unified API JSON in, JSON out ### How it works. - 01 #### Authenticate. Scoped API keys for service-to-service calls. OAuth for user-context flows. Same auth posture as the portal. - 02 #### Call. Verification or Data Production endpoint. JSON in, JSON out. - 03 #### Handle. The response is signed, logged, and replayable in your own systems. - 04 #### Audit. Every call writes to the same audit trail the portal does. One source of truth across both surfaces. FAQ ### Questions Everything about building on the Kodex API. Request a demo What is the Kodex API? The Kodex API is programmatic access to the network. The Verification API returns a real-time verification status for any law enforcement requester from one email lookup. The Targets API automates producing data on verified requests. Status webhooks tell you when a standing changes. Who is the API for? Teams that already have their own systems: legal and compliance teams with an in-house legal center, platforms embedding verification in their own product, and engineering teams that treat lawful data access as infrastructure. If you’d rather use a finished application, that’s Kodex Core. How does a lookup work? Send a requester’s email to the Verification API. It returns the agent’s standing, their agency’s status, and the domain’s risk level, checked against the Kodex Global Network in real time. One call, JSON in, JSON out. How is the API authenticated? With scoped API keys, sent in a request header. Keys are created and managed by your admins, and every call is logged to the same audit trail as the Kodex application. A demo environment is available for integration testing. Can we test before going live? Yes. Kodex provides a demo environment with test data, so your engineers can build and validate the integration end to end before production keys are issued. The interactive reference at docs.kodexapi.com lets you try calls in the browser. How do I get access? Talk to your Kodex account team, or reach out through the contact page. API access is provisioned per organization, with keys scoped to what your integration needs.