Lean Technologies Open Banking Parties API is one of 67 APIs that Lean Technologies publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Open Banking Parties. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes
1 operation
across 1 path,
and defines 26 schemas.
It is described by OpenAPI 3.1.0, at version v0.2.3.
Requests are made against 2 base URLs: https://sandbox.leantech.me, https://api2.leantech.me.
1 operations1 paths26 schemas1 GET
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.1.0
API Version
v0.2.3
Base URL
https://api2.leantech.me
Authentication
HTTP Bearer
Resource Areas
1
Authentication & Security 1
Lean Technologies Open Banking Parties API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
By default, every request must be authenticated.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.
The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are OBClaims (29 properties), OBDocumentDetails (8 properties), OBGetPartiesResponse (8 properties), OBPartyIdentityAddressClaim (6 properties). Each schema is shown below with its type and property counts.
OBPartyIdentityCheckDetail
object
Details of a check performed on PSU evidence for identity verification.
4 properties
OBVerificationAssuranceProcess
object
Assurance process that was followed to meet the requirements of the trust framework.
3 properties
OBPartyIdentityEvidenceDocumentType
string
The type of evidence provided for document-based identity verification.
OBParty
object
Unambiguous identification of the party.
6 properties4 required
OBPartyIdentityAddressClaim
object
Address object as per OpenID Connect Core 1.0 Address Claim.
6 properties
OBPartiesData
object
Container for the list of Open Banking parties at the entity level.
2 properties1 required
OBElectronicRecordTypeCode
string
The type of electronic record used for identity verification.
OBMeta
object
Metadata relevant to the resource.
1 property
OBVerification
object
Verification details for the identity claim (OpenID Connect for Identity Assurance 1.0).
6 properties1 required
OBPartyIdentityEvidenceTypeElectronicRecord
object
Electronic record evidence for PSU identity verification (OpenID Connect for Identity Assurance 1.0).
5 properties
OBPartyTypeCode
string
Specifies the type of party.
OBLinks
object
Links relevant to the resource for pagination navigation.
5 properties1 required
OBPartyIdentityEvidenceAttachment
object
Attachment related to PSU identity evidence (OpenID Connect for Identity Assurance 1.0).
4 properties
OBClaims
object
Standard and identity assurance claims for the party (OpenID Connect Core 1.0).
29 properties
OBAccountRoleCode
string
Specifies the role of the party in relation to the account.
OBPartyIdentityEvidenceElectronicRecordType
string
The type of evidence provided for electronic record-based identity verification.
OBDocumentTypeCode
string
The type of document used for evidence checking by the PASP.
OBVerificationEvidenceRef
object
Reference to a specific evidence transaction.
2 properties1 required
OBPartyCalendarType
string
The type of calendar used for dates in document or electronic record evidence.
OBGetPartiesResponse
object
Response envelope for the Open Banking entity-level parties.
8 properties4 required
OBPartyIdentityEvidenceTypeDocument
object
Document evidence for PSU identity verification (OpenID Connect for Identity Assurance 1.0).
6 properties
OBVerifiedClaim
object
Verified identity claim for a party (OpenID Connect for Identity Assurance 1.0).
2 properties2 required
OBStatusDetail
objectnull
2 properties
OBTrustFramework
string
Trust framework used to verify the party's identity claims.
OBDocumentDetails
object
The document used to perform the identity verification.
8 properties
OBVerificationAssuranceDetail
object
Details about how a specific piece of evidence complies with the assurance process policy.
3 properties
Specification
The full machine-readable OpenAPI contract behind this narrative.
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.
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 Lean Technologies Open Banking Parties 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.