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

The Status API from Lane API — 13 operation(s) for status.

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

This API exposes 17 operations across 13 paths, and defines 21 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.

17 operations 13 paths 21 schemas 1 DELETE4 GET9 PATCH3 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 Status 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 17

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

Status 17
GET
/dms/customer/status-flag
Get all customer status flag
get_all_status_flag_dms_customer_status_flag_get 1 param → 200422
POST
/dms/customer/status-flag
Create customer status flag
add_status_flag_dms_customer_status_flag_post body → 201422
DELETE
/dms/customer/status-flagdeprecated
Remove customer status flag
delete_status_dms_customer_status_flag_delete 1 param → 200422
PATCH
/dms/customer/remove-status-flag
Remove customer status flag
delete_status_flag_dms_customer_remove_status_flag_patch 1 param body → 200422
POST
/dms/configure/order-status/
Get orders record filtered on order status
get_orders_by_status_dms_configure_order_status__post body → 200422
PATCH
/dms/configure/order/update-status/{reference_number}
Update order status record by order reference number
update_order_status_by_reference_number_dms_configure_order_update_status__reference_number__patch 2 params body → 200422
POST
/dms/configure/order/status/
Update order status history record by order reference number
get_orders_status_history_dms_configure_order_status__post body → 200422
GET
/dms/configure/order/status-by-dealer
Get order status by dealer
get_order_status_by_delaer_id_and_reference_number_dms_configure_order_status_by_dealer_get 2 params → 200422
PATCH
/dms/order/update-payment-status/{reference_number}
Update Payment Status
update_payment_status_dms_order_update_payment_status__reference_number__patch 3 params → 200422
PATCH
/dms/order/change-proposal-status
Update order proposal status
update_proposal_status_dms_order_change_proposal_status_patch body → 200422
PATCH
/dms/configure/disclaimer-status
Update Disclaimer status
update_disclaimer_status_by_id_dms_configure_disclaimer_status_patch 2 params → 200422
GET
/dms/customer/document/status
Get customer document by identifier
get_customer_document_identifier_dms_customer_document_status_get 1 param → 200422
PATCH
/dms/customer/document/status
Update customer document status
update_customer_document_status_dms_customer_document_status_patch 1 param body → 200422
GET
/dms/customer/document/uploading-status
Get customer document upload status
get_customer_document_upload_status_dms_customer_document_uploading_status_get 1 param → 200422
PATCH
/dms/customer/document/uploading-status
Update customer document upload status
update_customer_document_uploading_status_dms_customer_document_uploading_status_patch 1 param body → 200422
PATCH
/dms/set-trade-in-inspection-status/{order_id}
Set Trade-in inspection status
set_trade_in_inspection_status_dms_set_trade_in_inspection_status__order_id__patch 2 params → 200422
PATCH
/dms/lead/change-status/{lead_id}
Update exisitng lead status
change_status_dms_lead_change_status__lead_id__patch 1 param body → 200422

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are CustomerDocumentResponseModel (24 properties), CustomerStatusFlagResponseModel (10 properties), OrderCommentsModel (9 properties), LeadModel (7 properties). Each schema is shown below with its type and property counts.

OrderStatusHistoryModel
object
1 property 1 required
ValidationError
object
3 properties 3 required
OrderCommentsModel
object
9 properties
LeadModel
object
7 properties
CommentDiaryCategory
string
An enumeration.
CustomerDocumentUploadStatus
object
1 property 1 required
CustomerStatusFlagResponseModel
object
10 properties
OrderStatusRequestModel
object
3 properties 2 required
CustomerDeleteModel
object
1 property 1 required
StatusResponseModel
object
2 properties
DeleteRequestModel
object
1 property 1 required
GetOrderStatusModel
object
1 property 1 required
CustomerDocumentResponseModel
object
24 properties
UpdateProposalStatusRequestModel
object
7 properties 3 required
OrderProposalStatus
string
An enumeration.
LeadData
object
3 properties
CustomerDocumentStatus
object
1 property 1 required
TradeInInspectionStatus
An enumeration.
HTTPValidationError
object
1 property
CustomerStatusFlagModel
object
5 properties 4 required
DocumentUploadStatus
string
An enumeration.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lane-api-status-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 Status 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.