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

Lead Bank Entity API

The Entity API from Lead Bank — 2 operation(s) for entity.

Lead Bank Entity 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 Entity. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 2 paths, and defines 63 schemas. It is described by OpenAPI 3.2.0, at version v1.0.

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

4 operations 2 paths 63 schemas 2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

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

Paths & Operations 4

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

Entity 4
POST
/v0/entities
Create an entity
create-an-entity 1 param body → 200400409422429500503
GET
/v0/entities
Retrieve an entity by client customer id
retrieve-an-entity-by-client-customer-id 1 param → 200400404429500503
PATCH
/v0/entities/{id}
Update an entity
Update-an-entity 2 params body → 200400404409422429500503
GET
/v0/entities/{id}
Retrieve an entity by entity id
retrieve-an-entity-by-entity-id 1 param → 200400404429500503

Schemas 63

The contract defines 63 schemas that model the data the API accepts and returns. The most detailed are CreateABusinessEntityResponse (16 properties), CreateASolePropEntityResponse (15 properties), CreateAnIndividualEntityResponse (14 properties), CreateABusinessEntityRequestBody (12 properties). Each schema is shown below with its type and property counts.

UpdateBusinessDetails
object
Details for the business entity
11 properties
InvalidParameterDetail
object
2 properties
CreateABusinessEntityRequestBody
object
12 properties 2 required
BusinessTypeEnum
string
Business Types. Possible business types are corporation, partnership, soleprop, llc, trust, cooperative, other. - For business entity, cannot use soleprop as b…
RoleDetails
object
3 properties
UpdateASolePropEntityRequestBody
object
10 properties 1 required
RfiDetailsResultEnum
string
Result of request for information with the end customer. Leave blank if RFI has not been sent to the customer.
KycDetails
object
Details on KYC on the entity.
2 properties 2 required
CreateAnIndividualEntityRequestBody
object
10 properties 2 required
RetrieveAnEntitySuccessResponse
TaxIdentification
object
2 properties 2 required
APIError
object
6 properties
NonUsEntityTypeEnum
string
Entity is considered non-US entity if they do not have US tax identification. For non-US entities, at least 1 government-verified identification documents is r…
IdentificationDetailsIndividual
object
NonUsEntityBusiness
object
2 properties 1 required
KycDetailsResultEnum
string
KYC result. Possible values: pending | passed | failed.
ContactMethodTypePhone
string
ContactMethodType = phonenumber. Conforms to E.123 standard
ContactMethodEmail
object
2 properties 2 required
IndividualDetails
object
Details for the individual entity
10 properties 3 required
UpdateIndividualDetails
object
Details for the individual entity
10 properties
Address
object
6 properties 3 required
ContactMethodPhone
object
2 properties 2 required
CreateAnIndividualEntityResponse
object
14 properties 4 required
IdentificationDocumentsTypeEnum
string
The entity's government-verified identification document type. This will apply for identification types other than US tax identification. - For individual enti…
UpdateABusinessEntityRequestBody
object
11 properties 1 required
UpdateAddressDetails
object
3 properties
TaxIdentificationTypeEnum
string
The entity's US tax identification type. - For individual entity, ssn or itin is required. - For business entity, ein is required. For single-member LLC entiti…
ContactMethod
object
UsEntityTypeEnum
string
Entity is considered US entity if they have US tax identification. For US entities, US tax identification number as well as other available government-verified…
AddressDetails
object
3 properties
CreateASolePropEntityRequestBody
object
11 properties 3 required
EntityTypeIndividual
string
Type of entity = individual.
SoleProprietor
object
1 property 1 required
IntendedRolesEnum
string
The entity's intended role. Lead highly recommends using this field to confirm data requirements for different roles to minimize errors later. In the event mor…
IdentificationDocument
object
7 properties 3 required
UsEntity
object
3 properties 1 required
EntityTypeSoleProp
string
Type of entity = soleprop.
BeneficialOwners
object
3 properties 1 required
CreateAnEntitySuccessResponse
OfacDetails
object
Details on OFAC on the entity.
2 properties 2 required
AdditionalDocumentTypeEnum
string
Type of additional non-government documents being provided to verify entity. Possible values are bankstatement, utilitybills, proofofaddress, investigationrepo…
UpdateAnEntityRequestBody
UpdateAddress
object
6 properties
RfiDetails
object
2 properties 2 required
OfacDetailsResultEnum
string
OFAC result. Possible values: pending | passed | failed.
NonUsEntityIndividual
object
2 properties 1 required
CreditDetails
object
Details on credit data from credit bureaus on the entity.
3 properties 3 required
EntityRiskScoreEnum
string
The entity's risk score, mapped to Lead by the client. Client should have provided risk score mapping to Lead.
EntityTypeBusiness
string
Type of entity = business.
CriteriaDetails
object
2 properties
CreateABusinessEntityResponse
object
16 properties 5 required
Metadata
object
A set of key-value pairs that can be used to store additional information related to this object.
AdditionalDocument
object
3 properties 1 required
ControlPersons
object
3 properties 2 required
BusinessDetails
object
Details for the business entity
11 properties 3 required
UpdateAnIndividualEntityRequestBody
object
9 properties 1 required
CreateASolePropEntityResponse
object
15 properties 6 required
CreateAnEntityRequestBody
ContactMethodTypeEmail
string
ContactMethodType = email.
CreditReportSourceEnum
string
The name of the credit bureau.
IdentificationDetailsBusiness
object
RoleDetailsStatus
string
Role Details Status
UpdateAnEntitySuccessResponse

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Lead Bank publishes across the network.

Lead Bank Lend API
Lead Bank Move API
Lead Bank Issue API
Lead Bank Store API
Lead Bank File Integrations (SFTP)
Lead Bank Webhooks
Lead Bank Account Number API
Lead Bank ACH API
Lead Bank Blockchain Payment API
Lead Bank Compliance API
Lead Bank Events API
Lead Bank Funding API
Where this information came from

This is an independent, third-party profile of Lead Bank Entity 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.