Skip to main content

​
Overview

The Conduit API provides programmatic access to Conduit Financial’s platform for customer onboarding, compliance, and payments.
Building with an AI assistant? These docs are LLM-readable. Add any page to your chat with the Copy page / Open in menu at the top of each page, point a tool at the documentation index at /llms.txt for page discovery or at the full corpus at /llms-full.txt, or connect the docs MCP server directly in Claude Code:

​
How Conduit Works

Conduit uses an application-based model. Instead of creating customers directly, you submit an application with the required information and documents. Conduit reviews the application — and if approved, a customer record is created automatically. This means your integration follows a submit-and-listen pattern:
  1. Authenticate — obtain an API key and set it on every request
  2. Check requirements — call the requirements endpoint to discover what fields and documents are needed for a given country
  3. Upload documents — upload KYB documents via the documents endpoint
  4. Submit an application — create an application with the required fields and document references
  5. Listen for webhooks — Conduit reviews the application and notifies you via webhook when it’s approved or rejected
  6. Customer is active — on approval, a customer record is created and returned in the webhook payload
The review process is automated. You do not need to poll for status — configure a webhook endpoint and Conduit will notify you.
Already running your own KYC program? If your organization has been enrolled in KYC reliance, you can upload verification reports from your own IDV provider instead of sending each control person through a Conduit-hosted identity flow. See the KYC reliance guide.

​
Examples use a consistent fictional org and customer

Every example in this site uses Aurora Robotics Inc. as the business, Aiko Tanaka as the individual, and a small pool of themed wallet and bank values. See Example data for the full palette. When an example illustrates a failure path, the wallet address or account number is replaced with a magic suffix that calls out the effect.

​
Base URL

Both environments expose the same API with the same authentication mechanism. See Authentication for details on environments.

​
What You’ll Need

Before you start integrating:
  • API key — generated from the Conduit dashboard
  • Webhook endpoint URL — a publicly accessible HTTPS URL where Conduit will send event notifications
  • KYB documents — business registration, operating license, and other documents required for the countries you operate in

​
Next Steps

  • Run the sandbox quickstart — zero to your first completed transaction with simulated money; the sandbox gives you deterministic controls for every flow on this site
  • Authentication — set up your API key and understand environments
  • Webhooks — configure webhook endpoints to receive real-time notifications
  • Crypto wallets — provision non-custodial wallets your customers sign with passkeys, or your backend signs with API keys
  • API Reference — conventions, error handling, and endpoint documentation