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

Vehicles.dev Control API

The Control API from Vehicles.dev — 23 operation(s) for control.

Vehicles.dev Control API is one of 10 APIs that Vehicles.dev publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 30 operations across 23 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 0.0.0.

Requests are made against a single base URL, https://api.vehicles.dev.

30 operations 23 paths 1 schemas 4 DELETE13 GET3 PATCH10 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.0
Base URL
https://api.vehicles.dev
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Vehicles.dev Control API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (Product API key) (apiKeyBearer). It accepts HTTP bearer tokens (WorkOS access token) (workosBearer).

Paths & Operations 30

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

Control 30
POST
/v1/control/bootstrap
provisionControlIdentity body → 200400401403404409429500
GET
/v1/control/account
getControlAccount → 200400401403404409429500
PATCH
/v1/control/account
updateControlAccount body → 200400401403404409429500
DELETE
/v1/control/account
deleteControlAccount body → 204400401403404409429500
GET
/v1/control/dashboard/actions
getControlDashboardActions → 200400401403404409429500
GET
/v1/control/billing/catalog
getControlBillingCatalog → 200400401403404409429500
GET
/v1/control/billing/summary
getControlBillingSummary → 200400401403404409429500
GET
/v1/control/billing/usage
getControlBillingUsage → 200400401403404409429500
GET
/v1/control/billing/orders
getControlBillingOrders 1 param → 200400401403404409429500
GET
/v1/control/billing/invoices
getControlBillingInvoices 1 param → 200400401403404409429500
POST
/v1/control/billing/checkout
createControlBillingCheckout body → 200400401403404409429500
POST
/v1/control/billing/subscription/checkout
createControlBillingSubscriptionCheckout body → 200400401403404409429500
POST
/v1/control/billing/subscription/change
changeControlBillingSubscription body → 200400401403404409429500
POST
/v1/control/billing/subscription/cancel
cancelControlBillingSubscription body → 200400401403404409429500
GET
/v1/control/members
listControlMembers → 200400401403404409429500
PATCH
/v1/control/members/{id}
updateControlMember 1 param body → 200400401403404409429500
DELETE
/v1/control/members/{id}
removeControlMember 1 param → 204400401403404409429500
GET
/v1/control/invitations
listControlInvitations → 200400401403404409429500
POST
/v1/control/invitations
createControlInvitation 1 param body → 201400401403404409429500
POST
/v1/control/invitations/accept
acceptControlInvitation body → 200400401403404409429500
DELETE
/v1/control/invitations/{id}
revokeControlInvitation 1 param → 204400401403404409429500
GET
/v1/control/api-keys
listControlApiKeys → 200400401403404409429500
POST
/v1/control/api-keys
createControlApiKey body → 201400401403404409429500
DELETE
/v1/control/api-keys/{id}
revokeControlApiKey 2 params → 204400401403404409429500
PATCH
/v1/control/api-keys/{id}
updateControlApiKey 1 param body → 200400401403404409429500
POST
/v1/control/history-reports
Order a dashboard vehicle history report
createControlVehicleHistoryReport 1 param body → 202400401402403404409429
GET
/v1/control/history-reports
List recent dashboard vehicle history reports
listControlVehicleHistoryReports → 200400401402403404409429
POST
/v1/control/history-reports/{id}/retry
Retry dashboard vehicle history report submission
retryControlVehicleHistoryReportSubmission 1 param → 202400401402403404409429
GET
/v1/control/history-reports/{id}
Poll dashboard vehicle history report status
getControlVehicleHistoryReportStatus 1 param → 200400401402403404409429
GET
/v1/control/history-reports/{id}/result
Retrieve a completed dashboard vehicle history report
getControlVehicleHistoryReportResult 1 param → 200400401402403404409429

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is def-0 (9 properties). Each schema is shown below with its type and property counts.

def-0
object
9 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vehicles-dev-api-control-api-openapi.yml Raw ↑

Other APIs Vehicles.dev publishes across the network.

Vehicles.dev Admin API
Vehicles.dev Billing API
Vehicles.dev Data API
Vehicles.dev Employment API
Vehicles.dev Operations API
Vehicles.dev Operator API
Vehicles.dev Reports API
Vehicles.dev Vehicles API
Vehicles.dev Webhooks API
Where this information came from

This is an independent, third-party profile of Vehicles.dev Control 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.