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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Lane API

Lane API History API

Manage operations related to History

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 10 operations across 10 paths, and defines 25 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.

10 operations 10 paths 25 schemas 10 GET

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
Contact
support@netsolapp.io, support@appexnow.com
Resource Areas
1

Authentication & Security 2

Lane API History 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 10

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

History 10

Manage operations related to History

GET
/dms/customer/customer-history
Get all customers records history
get_customer_history_dms_customer_customer_history_get 3 params → 200422
GET
/dms/customer/license-info-history
Get all customer license information history
get_license_information_history_dms_customer_license_info_history_get 5 params → 200422
GET
/dms/customer/third-party-response-history
Get third party response history
get_third_part_response_history_dms_customer_third_party_response_history_get 5 params → 200422
GET
/dms/address/history
Delete existing record of address
address_history_dms_address_history_get 2 params → 200422
GET
/dms/customer/insurance-information-historydeprecated
Get customer insurance information history
get_insurance_information_history_dms_customer_insurance_information_history_get 5 params → 200422
GET
/dms/customer/insurance-information/document-history
Get customer insurance information document history
get_insurance_documents_dms_customer_insurance_information_document_history_get 1 param → 200422
GET
/dms/order/order-checklist-update-history
Get Order Checklist Update History
get_order_checklist_update_history_dms_order_order_checklist_update_history_get 3 params → 200422
GET
/dms/customer/document-history
Get customer document history
get_customer_document_history_dms_customer_document_history_get 5 params → 200422
GET
/dms/history
Get all customers records history
get_customer_all_history_dms_history_get 7 params → 200422
GET
/dms/history-details
Get history detail
history_detail_dms_history_details_get 3 params → 200422

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are CustomerProfileModelResponse (29 properties), LicenseInfoResponseModel (26 properties), CustomerDocumentWithReviewsResponseModel (25 properties), InsuranceInformationResponseModel (24 properties). Each schema is shown below with its type and property counts.

CustomerAddressWithoutAddressTypeModel
object
11 properties
ValidationError
object
3 properties 3 required
CustomerAddressPreResponseModel
object
18 properties 1 required
InsuranceDetailStatus
string
An enumeration.
InsuranceInfoPaginationResponse
object
5 properties
AddressResponseModel
object
20 properties 1 required
AddressTypesEnum
string
An enumeration.
LicenseInfoPaginationResponse
object
5 properties
InsuranceDocumentsResponseModel
object
10 properties
HistoryPaginationResponse
object
5 properties
ComparisonModule
string
An enumeration.
LicenseInfoCustomerResponseModel
object
9 properties
HistoryResponseDetail
object
10 properties
CustomerProfileModelResponse
object
29 properties
CustomerEmploymentInfoPreResponseModel
object
14 properties
CallType
string
An enumeration.
AddressTypes
string
An enumeration.
LicenseInfoResponseModel
object
26 properties
HTTPValidationError
object
1 property
InsuranceInformationResponseModel
object
24 properties
CustomerStipulationPaginationResponse
object
5 properties
CustomerDocumentWithReviewsResponseModel
object
25 properties 1 required
CustomerDocumentReviewPreResponseModel
object
7 properties
CustomerPaymentInfoResponseModel
object
13 properties
AddressBasicModel
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Lane API publishes across the network.

Lane API Accord API
AE Profile APIs.io
Lane API Add API
AE Profile APIs.io
Lane API Additional API
AE Profile APIs.io
Lane API Address API
AE Profile APIs.io
Lane API Affordability API
AE Profile APIs.io
Lane API Agreement API
AE Profile APIs.io
Lane API Allowed API
AE Profile APIs.io
Lane API An API
AE Profile APIs.io
Lane API Analytics API
AE Profile APIs.io
Lane API Appointment API
AE Profile APIs.io
Lane API Appointment Management API
AE Profile APIs.io
Lane API Approve API
AE Profile APIs.io
#History
← Back to L APIs
API Details
ID
lane-api:lane-api-history-api
Server
https://dms-api.netsolapp.io
Docs
https://docs.netsolapp.io/lane/index.html
Provider
Lane API
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

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.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=lane-api-history-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/lane-api-history-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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 Lane API History 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.