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 Links API

Payment link management operations

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

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

6 operations 4 paths 18 schemas 4 GET1 POST1 PUT

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

Paths & Operations 6

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

Payment Links 6

Payment link management operations

POST
/payment-links/v1
Create Payment Link
createPaymentLink body → 201
GET
/payment-links/v1
List Payment Links
getPaymentLinks 2 params → 200
GET
/payment-links/v1/{payment_link_id}
Get Payment Link
getPaymentLink 1 param → 200
PUT
/payment-links/v1/{payment_link_id}
Update Payment Link
updatePaymentLink 1 param body → 200
GET
/payment-links/v1/{payment_link_id}/usages
List Payment Link Usages
listPaymentLinkUsages 3 params → 200
GET
/payment-links/v1/{payment_link_id}/usages/{usage_id}
Get Payment Link Usage
getPaymentLinkUsage 2 params → 200

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are PaymentLinkResponse (11 properties), CreatePaymentLinkRequest (7 properties), PaymentLinkUsageDetails (7 properties), PaymentDetailsRequest (5 properties). Each schema is shown below with its type and property counts.

PaymentDetailsResponse
object
The payment parameters attached to this link. These values are fixed for the lifetime of the link.
5 properties 3 required
CreatePaymentLinkRequest
object
Configuration for a new payment link. Provide paymentdetails at minimum. Use maxusages or expiresat to limit availability.
7 properties 1 required
IdentifierResponse
object
An additional field configured to be collected from payers at payment time.
4 properties 1 required
Currency
string
The ISO 3 letter currency code
PaymentDetailsRequest
object
The payment parameters that apply to every transaction made through this link. Fixed at creation time and cannot be changed afterwards.
5 properties 3 required
PageMetadata
object
Metadata about the current page of results
5 properties 4 required
IdentifierType
string
The type of information to collect from the payer. Controls input validation and formatting in the payment UI. - EMAIL: Collects an email address. Input is val…
IdentifierRequest
object
An additional field to collect from the payer at payment time, such as an email address, phone number or a custom reference.
4 properties 1 required
PaymentLinkResponse
object
The full state of a payment link, including its shareable URL, current status, usage counts, and configuration.
11 properties 6 required
UpdatePaymentLinkRequest
object
Request payload for updating a payment link
1 property 1 required
PaymentLinkStatus
string
The lifecycle state of a payment link. - ACTIVE: The link is live and will accept payments. This is the initial state after creation. - EXPIRED: The link's exp…
PaymentPurposeCode
string
A category code that relates to the type of services or goods that corresponds to the underlying purpose of the payment. The code must conform to the payment p…
CollectedIdentifier
object
A single identifier value collected from the payer.
3 properties 3 required
PaymentLinkUsageDetails
object
Details of a payment link usage, including payer-provided identifiers and payment outcome.
7 properties 4 required
UpdatePaymentLinkStatus
string
The target status to set on a payment link. Only ACTIVE and DISABLED transitions are permitted via the update endpoint. - ACTIVE: Re-enables a previously disab…
UsageStatus
string
Lifecycle status of the payment link usage. - STARTED: Payment flow initiated; payment intent created; waiting for bank confirmation. - PAYMENTCREATED: Bank co…
PaymentLinkUsageList
object
A single page of payment link usages. Use the page object for total counts and paginate with the page and size query parameters.
2 properties 2 required
PaymentLinkListResponse
object
A single page of payment links. Use the page object for total counts and paginate with the page and size query parameters.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lean-technologies-payment-links-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 Links 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.