Loadsmart · Schema
AssetVisit
FreightLogisticsTransportationSupply ChainDigital FreightFreight BrokerageTruckloadLTLDrayageFlatbedMulti-ModalTMSDock SchedulingYard ManagementWarehouse4PLFreightTech
Properties
| Name | Type | Description |
|---|---|---|
| id | string | The unique identifier of the record |
| createDateTime | string | The date and time when the record was created |
| createdBy | object | The ID of the user who created the record |
| lastChangedDateTime | string | The date and time when the record was last changed |
| orgId | string | |
| warehouseId | string | The id of the warehouse |
| appointmentId | string | The id of the appointment |
| secondaryAppointmentId | string | The id of the secondary appointment |
| companyId | string | The id of the company |
| phone | string | The phone number of the driver |
| isPlanned | boolean | Indicates if the visit has an appointment or not |
| companyHint | string | A free-text to indicate the company name when there is no appointment |
| driverNotes | string | Notes typed by the driver when checking in |
| driverAppointmentIdentifier | string | Appointment identification typed by the driver when checking in |
| visitType | object | |
| checkInAcknowledged | boolean | Whether the check-in was acknowledged by the warehouse or not |
| rejectReason | object | The reason the asset visit was rejected |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/loadsmart/json-schema/loadsmart-asset-visit-schema.json",
"title": "AssetVisit",
"x-generated": "2026-10-29",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/loadsmart-asset-visit-api-openapi.yml#/components/schemas/AssetVisit",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "The unique identifier of the record",
"readOnly": true
},
"createDateTime": {
"format": "date-time",
"type": "string",
"description": "The date and time when the record was created",
"readOnly": true
},
"createdBy": {
"type": "object",
"description": "The ID of the user who created the record",
"readOnly": true
},
"lastChangedDateTime": {
"format": "date-time",
"type": "string",
"description": "The date and time when the record was last changed",
"readOnly": true
},
"orgId": {
"type": "string",
"format": "uuid"
},
"warehouseId": {
"type": "string",
"format": "uuid",
"description": "The id of the warehouse"
},
"appointmentId": {
"type": "string",
"format": "uuid",
"description": "The id of the appointment"
},
"secondaryAppointmentId": {
"type": "string",
"format": "uuid",
"description": "The id of the secondary appointment"
},
"companyId": {
"type": "string",
"format": "uuid",
"description": "The id of the company"
},
"phone": {
"type": "string",
"description": "The phone number of the driver"
},
"isPlanned": {
"type": "boolean",
"description": "Indicates if the visit has an appointment or not"
},
"companyHint": {
"type": "string",
"description": "A free-text to indicate the company name when there is no appointment"
},
"driverNotes": {
"type": "string",
"description": "Notes typed by the driver when checking in"
},
"driverAppointmentIdentifier": {
"type": "string",
"description": "Appointment identification typed by the driver when checking in"
},
"visitType": {
"$ref": "#/$defs/AssetVisitType"
},
"checkInAcknowledged": {
"type": "boolean",
"description": "Whether the check-in was acknowledged by the warehouse or not"
},
"rejectReason": {
"type": "object",
"description": "The reason the asset visit was rejected"
}
},
"required": [
"id",
"createDateTime",
"createdBy",
"lastChangedDateTime",
"orgId",
"warehouseId",
"phone",
"isPlanned"
],
"$defs": {
"AssetVisitType": {
"type": "string",
"description": "The type of the asset visit",
"enum": [
"LiveUnload",
"LiveLoad",
"Live",
"Drop",
"PickUp",
"DropHook",
"Unknown"
]
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/loadsmart-asset-visit"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.