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

Lean Technologies Payment Destination API

The Payment Destination API from Lean Technologies — 3 operation(s) for payment destination.

Lean Technologies Payment Destination 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 Payment Destination. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 3 paths, and defines 2 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.

4 operations 3 paths 2 schemas 3 GET1 POST

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 Payment Destination API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 4

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

Payment Destination 4
POST
/payments/v1/destinations
Create Payment Destination
createPaymentDestination body → 200
GET
/payments/v1/destinations
List Payment Destinations
getPaymentDestinations → 200
GET
/payments/v1/destinations/{payment_destination_id}
Get Payment Destination by ID
getPaymentDestinationById 1 param → 200
GET
/customers/v1/{customer_id}/destinations
Get Payment Destinations for Customer
getPaymentDestinationsByCustomerId 1 param → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are PaymentDestination (19 properties), CustomerPaymentDestination (13 properties). Each schema is shown below with its type and property counts.

CustomerPaymentDestination
object
13 properties 10 required
PaymentDestination
object
19 properties 9 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lean-technologies-payment-destination-api-openapi.yml Raw ↑

Other APIs Lean Technologies publishes across the network.

Lean Technologies Account Controls (New) API
Lean Technologies Account On File API
Lean Technologies Accounts Raw Data API
Lean Technologies Assets API
Lean Technologies Balance Raw Data API
Lean Technologies Balances API
Lean Technologies Bank API
Lean Technologies Bank Statements Report API
Lean Technologies Banks API
Lean Technologies Behavioral Insights (New) API
Lean Technologies Beneficiaries Raw Data API
Lean Technologies Beneficiary Name Verification API
Where this information came from

This is an independent, third-party profile of Lean Technologies Payment Destination 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.