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

Lane API Payments API

The Payments API from Lane API — 8 operation(s) for payments.

Lane API Payments API is one of 177 APIs that Lane API publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 11 operations across 8 paths, and defines 13 schemas. It is described by OpenAPI 3.0.2, at version 1.3.43.

Requests are made against a single base URL, https://dms-api.netsolapp.io.

11 operations 8 paths 13 schemas 1 DELETE2 GET1 PATCH6 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.2
API Version
1.3.43
Server
https://dms-api.netsolapp.io
Authentication
API Key, OAuth 2.0
Resource Areas
1

Authentication & Security 2

Lane API Payments API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Api-Key (APIKeyHeader). It supports OAuth 2.0 (OAuth2PasswordBearer) using the password flow.

Paths & Operations 11

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

Payments 11
GET
/dms/customer/payment-information
Get customer payment information
get_customer_payment_info_by_dms_customer_payment_information_get 1 param → 200422
POST
/dms/customer/payment-information
Create customer payment information
add_customer_payment_info_dms_customer_payment_information_post body → 201422
DELETE
/dms/customer/payment-information
Delete customer payment information
delete_customer_payment_info_by_id_dms_customer_payment_information_delete 1 param → 200422
PATCH
/dms/customer/payment-information
Update customer payment information
update_customer_payment_dms_customer_payment_information_patch body → 200422
POST
/dms/affordability-check/monthly-payment-calculation/V2/
Monthly Payment Calculation V2
monthly_payment_calculation_v2_dms_affordability_check_monthly_payment_calculation_V2__post body → 200422
GET
/dms/get-payment-methods/{reference_number}
Get Payment Methods & Get Paid Amount
get_payment_methods_dms_get_payment_methods__reference_number__get 1 param → 200422
POST
/dms/plaid-link-token/
Create Link Token
create_plaid_link_token_dms_plaid_link_token__post body → 200422
POST
/dms/create-payment/
Create payment for new Order
create_customer_order_dms_create_payment__post body → 200422
POST
/dms/update-payment/
Update Order Payment
update_payment_status_dms_update_payment__post → 200
POST
/dms/add-payment-details/
Add Payment Details from dealer side
add_payment_details_dms_add_payment_details__post body → 200422
PUT
/dms/remove-payment-details/{order_payment_detail_id}
Remove the order payment detail
remove_payment_details_dms_remove_payment_details__order_payment_detail_id__put 1 param → 200422

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are CreatePaymentResponse (16 properties), CustomerPaymentInformationResponseModel (14 properties), CustomerPaymentModelTypeMandatory (8 properties), MonthlyPaymentCalculationModelV2 (8 properties). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
ValidationError
object
3 properties 3 required
CustomerPaymentInformationResponseModel
object
14 properties 1 required
CreatePayment
object
8 properties 3 required
PaymentOption
object
3 properties
ResponseModel
object
1 property 1 required
PlaidLinkTokenResponseModel
object
3 properties 3 required
AddPaymentDetails
object
6 properties 2 required
MonthlyPaymentCalculationModelV2
object
8 properties 8 required
CustomerPaymentModelTypeMandatory
object
8 properties 2 required
CreatePaymentResponse
object
16 properties
CreatePlaidLinkToken
object
1 property 1 required
PaymentMethodType
string
An enumeration.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lane-api-payments-api-openapi.yml Raw ↑

Other APIs Lane API publishes across the network.

Lane API Accord API
Lane API Add API
Lane API Additional API
Lane API Address API
Lane API Affordability API
Lane API Agreement API
Lane API Allowed API
Lane API An API
Lane API Analytics API
Lane API Appointment API
Lane API Appointment Management API
Lane API Approve API
Where this information came from

This is an independent, third-party profile of Lane API Payments 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.