How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Lead Bank

Lead Bank Compliance API

The Compliance API from Lead Bank — 11 operation(s) for compliance.

Documentation Provider Profile APIs.io OpenAPI GitHub

Lead Bank Compliance API is one of 22 APIs that Lead Bank publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Compliance. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 13 operations across 11 paths, and defines 51 schemas. It is described by OpenAPI 3.0.1, at version v1.0.

Requests are made against 2 base URLs: https://api.sandbox.lead.bank, https://api.lead.bank.

13 operations 11 paths 51 schemas 1 DELETE4 GET2 PATCH6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
v1.0
Base URL
gated-partner-access
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Lead Bank Compliance API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 13

Across 11 paths, the API surfaces 13 operations — 1 DELETE, 4 GET, 2 PATCH, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Compliance 13
POST
/v0/applications
Create an application
create-an-application 1 param body → 200400401403409422429500
GET
/v0/applications/{id}
Retrieve an application
retrieve-an-application 1 param → 200400401403404429500
PATCH
/v0/applications/{id}
Update an application
update-an-application 2 params body → 200400401403404409422429
GET
/v0/applications/{id}/entity_relationships
List application entity relationships
list-application-entity-relationships 3 params → 200400401404429500
POST
/v0/accounts
Create an account
create-an-account 1 param body → 200400401403422429500
GET
/v0/accounts/{id}
Retrieve an account
retrieve-an-account 1 param → 200400401403404429500
PATCH
/v0/accounts/{id}
Update an account
update-an-account 2 params body → 200400401403404422429500
POST
/v0/accounts/{id}/activate
Activate an account
activate-an-account 2 params → 200400401403404422429500
POST
/v0/accounts/{id}/deactivate
Deactivate an account
deactivate-an-account 2 params body → 200400401403404422429500
POST
/v0/accounts/{id}/close
Close an account
close-an-account 2 params body → 200400401403404422429500
GET
/v0/accounts/{id}/entity_relationships
List account entity relationships
list-account-entity-relationships 3 params → 200400401404429500
DELETE
/v0/accounts/{id}/entity_relationships/{entity_id}
Delete account entity relationship
delete-account-entity-relationship 3 params → 200400401404422429500
POST
/v0/accounts/{id}/entity_relationships/batch
Batch create account entity relationships
batch-create-account-entity-relationships 2 params body → 200400401403404409422429

Schemas 51

The contract defines 51 schemas that model the data the API accepts and returns. The most detailed are Account (12 properties), PatchAccountCredit (9 properties), CreateAccountCredit (9 properties), AccountCredit (9 properties). Each schema is shown below with its type and property counts.

AccountDeactivateRequest
object
Request body for deactivating an account
1 property 1 required
ComplianceCurrencyCode
string
A three-letter currency code as defined in ISO 4217
AccountDetails
object
Core details of the account
4 properties
EntityID
string
The ID of your entity.
AccountCredit
object
Details specific to credit-based accounts
9 properties
AccountCloseRequest
object
Request body for closing an account
1 property 1 required
Decision
object
Decision-related information for the application
3 properties 2 required
Metadata
object
A set of key-value pairs that can be used to store additional information related to this object.
CreateComplianceDocument
object
Document reference for creating applications and accounts. One of displayedat or consentedat is required depending on document type: - displayedat: Required fo…
5 properties 2 required
CreateApplicationEntities
object
Entity relationships for the application. Maximum 20 entities per relationship type. Authorized signers required for commercial account holders.
3 properties 1 required
PatchAccountDetails
object
Details for updating an account
3 properties
CreditReport
object
Credit report information (Application only)
3 properties 3 required
APIError
object
6 properties
PatchApplicationCredit
object
Credit details for updating an application (all fields optional)
7 properties
EntityRelationshipType
string
Indicates the type of Entity
ApplicationComplianceDocument
object
Document reference associated with an application (response, all properties optional)
5 properties
CreateAccountRequest
object
Request body for creating a new account
6 properties 4 required
AccountCapability
string
Capability that informs Lead how the Account will be used
ApplicationAdverseActionNotice
object
Adverse action notice information (response, all properties optional)
3 properties
ApplicationID
string
Unique identifier for the application. Prefixed with application.
CreateApplicationDetails
object
Details for creating an application
3 properties 2 required
CreateAccountDetails
object
Details for creating an account
3 properties 1 required
ComplianceDocumentType
string
Type of document associated with an application
ApplicationEntities
object
Entity relationships associated with the application (response only)
3 properties
PatchAccountCredit
object
Details specific to credit-based accounts (for PATCH - all fields optional)
9 properties
ApplicationDetails
object
Application details (response, all properties optional)
3 properties
CreateAccountEntities
object
Entity relationships for the account (POST request only). Maximum 20 entities per relationship type. Cannot mix individual and business/soleprop entities in ac…
3 properties 1 required
CreateApplicationRequest
object
Request body for creating a new application in terminal status
6 properties 5 required
ApplicationCreditReport
object
Credit report information (response, all properties optional)
3 properties
PatchApplicationDetails
object
Details for updating an application (all fields optional)
3 properties
AccountStatus
string
Current state of the account
ApplicationDecision
object
Decision-related information (response, all properties optional)
3 properties
Application
object
An application object representing a credit application
9 properties
PatchAccountRequest
object
Request body for updating an existing account
5 properties
Scra
object
SCRA (Servicemembers Civil Relief Act) details
2 properties 1 required
AccountID
string
The ID of the Account object.
BatchCreateEntityRelationshipsRequest
object
Request body for batch creating entity relationships on an account.
2 properties 2 required
AdverseActionNotice
object
Adverse action notice information
3 properties 3 required
ComplianceDocument
object
Document reference associated with an application (response schema - all fields optional)
5 properties
AccountCloseStatusReason
string
Valid reasons for closing an account
AccountDeactivateStatusReason
string
Valid reasons for deactivating an account
CreateAccountCredit
object
Details specific to credit-based accounts (for POST - all fields required)
9 properties 7 required
InvalidParameterDetail
object
2 properties
AccountStatusReason
string
Machine-readable reason for the current status
ApplicationCredit
object
Credit details for an application (response, all properties optional)
7 properties
CreateApplicationCredit
object
Credit details for creating an application
7 properties 3 required
ApplicationStatus
string
Terminal state of the application. Possible values: approved, declined, canceled.
AccountEntities
object
Entity relationships associated with the account (response only)
1 property
EntityRelationship
object
Common fields for entity relationships
2 properties 2 required
Account
object
An account object
12 properties
PatchApplicationRequest
object
Request body for updating an existing application
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lead-bank-compliance-api-openapi.yml Raw ↑

Other APIs Lead Bank publishes across the network.

Lead Bank Lend API
AE Profile APIs.io
Lead Bank Move API
AE Profile APIs.io
Lead Bank Issue API
AE Profile APIs.io
Lead Bank Store API
AE Profile APIs.io
Lead Bank File Integrations (SFTP)
AE Profile APIs.io
Lead Bank Webhooks
AE Profile APIs.io
Lead Bank Account Number API
AE Profile APIs.io
Lead Bank ACH API
AE Profile APIs.io
Lead Bank Blockchain Payment API
AE Profile APIs.io
Lead Bank Entity API
AE Profile APIs.io
Lead Bank Events API
AE Profile APIs.io
Lead Bank Funding API
AE Profile APIs.io
#Compliance
← Back to L APIs
API Details
ID
lead-bank:lead-bank-compliance-api
Base URL
gated-partner-access
Docs
https://docs.lead.bank/api-integrations/overview
Provider
Lead Bank
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=lead-bank-compliance-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/lead-bank-compliance-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Lead Bank Compliance API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.