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

RunBuggy Vehicle Transfer Orders API

The Vehicle Transfer Order operations.

RunBuggy Vehicle Transfer Orders API is one of 6 APIs that RunBuggy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 9 operations across 7 paths, and defines 38 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://ng-staging.runbuggy.com/staging/api.

9 operations 7 paths 38 schemas 6 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://ng-staging.runbuggy.com/staging/api
Authentication
API Key
Contact
Terms of Service
Resource Areas
1

Authentication & Security 1

RunBuggy Vehicle Transfer Orders API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Authorization).

  • Authorization — See the [Authentication Guide](/docs/shipping/b6b6c2d4906e9-authentication).

Paths & Operations 9

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

Vehicle Transfer Orders 9

The Vehicle Transfer Order operations.

GET
/vehicle-transfer-orders
Find vehicle transfer orders
findVehicleTransferOrdersPaginatedUsingGET 4 params → 200401403404
GET
/vehicle-transfer-orders/{id}
Retrieve a vehicle transfer order
getVehicleTransferOrderUsingGET 1 param → 200401403404
PATCH
/vehicle-transfer-orders/{id}
Update a vehicle transfer order
updateVehicleTransferOrderUsingPATCH 1 param body → 202400401403
GET
/vehicle-transfer-orders/{id}/expanded
Get expanded vehicle transfer order
getExpandedUsingGET 1 param → 200401403404
GET
/vehicle-transfer-orders/expanded
Find vehicle transfer orders expanded
findVehicleTransferOrdersExpandedPaginatedUsingGET 4 params → 200401403404
POST
/vehicle-transfer-orders/gate-passes
Create a gate pass
createGatePassUsingPOST body → 200201401403404
GET
/vehicle-transfer-orders/{id}/gate-passes
Get gate passes
getGatePassesUsingGET 1 param → 200401403404
POST
/vehicle-transfer-orders/{id}/gate-passes
Add a gate pass
addGatePassUsingPOST 1 param body → 200201401403404
GET
/vehicle-transfer-orders/{id}/gate-passes/{passId}
Retrieve a gate pass
getGatePassUsingGET 2 params → 200401403404

Schemas 38

The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are VehicleTransferOrder (22 properties), VehicleTransferOrderExpanded (22 properties), Order (18 properties), Vehicle (14 properties). Each schema is shown below with its type and property counts.

FareItem
object
Order Fare Item
3 properties
Replacement
object
4 properties
VehicleMeasurements
object
5 properties
Canceled
object
3 properties
VehicleTransferOrderPatch
object
5 properties
Company
object
3 properties
InspectionSummary
object
4 properties
DirectionsPatch
object
2 properties
EstimatedTimeToArrival
object
6 properties
Item
object
2 properties
Attachment
object
5 properties
Event
object
2 properties
Contact
object
2 properties
VehicleTransferOrder
object
A Vehicle Transfer Order.
22 properties 8 required
Created
object
4 properties
Distance
object
3 properties
Error
object
A common Error object.
3 properties 1 required
VehicleTransferOrderIds
object
1 property 1 required
States
object
4 properties
Fare
object
5 properties
Pageable
object
6 properties
Sort
object
3 properties
TruckSpecifications
object
1 property
State
object
1 property
DetailedDirections
object
3 properties
PageVehicleTransferOrder
object
11 properties 11 required
TempFile
object
1 property
VehiclePatch
object
3 properties
Order
object
18 properties 6 required
Vehicle
object
When creating an order, there are 2 options for providing the Vehicle information. [See here](/docs/shipping/ace1edcc412ad-vehicle-request-requirements)
14 properties 1 required
VehicleTransferOrderExpanded
object
A Vehicle Transfer Order.
22 properties 7 required
Geolocation
object
2 properties
PageVehicleTransferOrderExpanded
object
11 properties 11 required
Window
object
4 properties
AddressComponents
object
8 properties
Location
object
11 properties 1 required
LocationPatch
object
3 properties
StateLocation
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

runbuggy-vehicle-transfer-orders-api-openapi.yml Raw ↑

Other APIs RunBuggy publishes across the network.

RunBuggy Data Science MCP Server
RunBuggy Companies API
RunBuggy Orders API
RunBuggy Token API
RunBuggy Webhooks API
Where this information came from

This is an independent, third-party profile of RunBuggy Vehicle Transfer Orders 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.