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

The Signatures API from Lane API — 3 operation(s) for signatures.

Lane API Signatures 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 Signatures. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

6 operations 3 paths 8 schemas 1 DELETE2 GET1 PATCH2 POST

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 Signatures 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 6

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

Signatures 6
GET
/dms/customer/signature
Gets a customer signature record by customer signature id
findone_customer_signature_dms_customer_signature_get 1 param → 200422
POST
/dms/customer/signature
Creates customer signature
add_customer_signature_dms_customer_signature_post body → 201422
DELETE
/dms/customer/signaturedeprecated
Deprecate signature delete enpoint. Use [delete-signature] instead
delete_customer_signature_deprecated_dms_customer_signature_delete 1 param body → 200422
PATCH
/dms/customer/signature
Updates customer signature
update_customer_signature_dms_customer_signature_patch 2 params body → 200422
GET
/dms/customer/signature/by-dealer-id
Gets a customer signature record by dealer id
findone_customer_signature_by_dealer_dms_customer_signature_by_dealer_id_get 1 param → 200422
POST
/dms/customer/document/signature-document
Customer Document Signature
signature_document_dms_customer_document_signature_document_post body → 200422

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are CustomerSignatureResponseModel (10 properties), CustomerSignatureModel (5 properties), CustomerSignatureUpdateModel (4 properties), SignatureCustomerDocument (4 properties). Each schema is shown below with its type and property counts.

CustomerSignatureResponseModel
object
10 properties
HTTPValidationError
object
1 property
ValidationError
object
3 properties 3 required
CustomerSignatureUpdateModel
object
4 properties
SignatureCustomerDocument
object
4 properties 4 required
CustomerSignatureModel
object
5 properties
ResponseModel
object
1 property 1 required
DeleteRequestModel
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lane-api-signatures-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 Signatures 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.