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

Augment Load Management API

API endpoints for creating, updating, and retrieving loads.

Augment Load Management API is one of 6 APIs that Augment publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Load Management. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 4 operations across 2 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version 20.0.1.

Requests are made against a single base URL, https://api.prod.goaugment.com.

4 operations 2 paths 32 schemas 1 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
20.0.1
Base URL
https://api.prod.goaugment.com
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Augment Load Management API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (httpBasic). By default, every request must be authenticated.

  • httpBasic — Authenticate with HTTP Basic auth by sending an empty username and your API key as the password, equivalent to encoding : in the Basic credential.

Paths & Operations 4

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

Load Management 4

API endpoints for creating, updating, and retrieving loads.

GET
/v2/loads
Get load by load number
getLoad 1 param → 200400401404
POST
/v2/loads
Create or update load
createOrUpdateLoad body → 204400
PATCH
/v2/loads
Patch a load
patchLoad body → 204400401404
POST
/v2/loads/tracking
Add a tracking event
addTrackingEvent body → 204400

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are LoadV2Response (42 properties), Load (30 properties), RouteStop (15 properties), LoadRouteStop (15 properties). Each schema is shown below with its type and property counts.

Load
object
30 properties 4 required
LoadNote
object
3 properties 3 required
RouteStop
object
A stop in the load route
15 properties 3 required
TrackingEventRequest
object
2 properties 2 required
LoadStatus
LoadPatchRequest
object
2 properties 2 required
LoadPatchOperation
Brokerage
object
1 property
AccessorialsEnum
string
Accessorial code representing an additional service or requirement for a load. This is not a closed set — new accessorial codes may be added at any time. Value…
ApiErrorBody
object
3 properties 1 required
PackageType
string
ExternalTrackingStatus
object
4 properties 4 required
LoadCustomer
object
Customer associated with the load
3 properties 1 required
LoadItem
object
13 properties 2 required
LoadV2Response
object
Enriched load data including tracking events, reference numbers, notes, customers, and shipment information.
42 properties 13 required
LoadRequest
object
6 properties 2 required
InputDateTimeUtc
string
TrackingEvent
object
14 properties 3 required
LoadReferenceNumberName
ExternalTrackingStatusCode
Status code indicating the current state of external tracking
TrackingEventContact
object
Contact information for a person associated with a tracking event.
5 properties
Carrier
object
8 properties 2 required
CarrierContact
object
Optional contact object. If provided, role is required.
6 properties 1 required
CarrierPaymentStatus
object
6 properties 2 required
LoadCustomData
object
Optional client-specific metadata for the load. Use string keys; each value may be a string, number, boolean, array of JSON-safe values, or a nested object wit…
LoadService
LoadShipment
object
13 properties 1 required
CommodityItem
object
A commodity item on the load
11 properties
LoadRouteStop
object
15 properties 5 required
Customer
object
2 properties 1 required
LoadItemUnit
object
2 properties 2 required
CarrierAddress
object
Carrier address on a load. Optional on the parent object; when present, include every required field below.
8 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

augment-load-management-api-openapi.yml Raw ↑

Other APIs Augment publishes across the network.

Augment API Key API
Augment Carrier Management API
Augment Carrier Support API
Augment Webhook Endpoints API
Augment Webhook Event Subscriptions API
Where this information came from

This is an independent, third-party profile of Augment Load Management 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.