Alvys API: AI Automations for Freight Operations
A POD hits Alvys; Carly can start the billing handoff before anyone checks the board. Alvys becomes the operating signal—loads, trips, drivers, carriers, equipment, documents, tracking, settlements, and change events—and Carly runs the customer updates, document chases, detention follow-up, and dispatch briefs around it.
The freight workflows the API unlocks
Freight operations produce plenty of data; the delay is usually between the event and the person who notices it.
- Proof of delivery starts billing. A POD upload can notify billing, attach the document to the load, and open the invoice checklist immediately.
- Load changes reach the right desk. A changed appointment, rate, stop, or carrier assignment can alert operations with the old and new values rather than making someone compare screens.
- Detention gets documented while it is recoverable. Arrival and departure changes can start a clock, gather the relevant records, and create a follow-up before the paperwork goes cold.
- Carrier onboarding becomes a controlled checklist. Pull the carrier record and documents, flag what is missing, and route exceptions to a human instead of emailing the same packet five times.
- Settlement discrepancies surface before payout. Compare invoices, deductions, carrier pay, and customer pay, then produce a review queue for anything outside tolerance.
The common thread is not “ask AI about my freight.” It is “Alvys already knows something changed; start the next job now.”
API access and authentication
Alvys uses OAuth 2.0 client credentials for machine-to-machine access. In Admin → API Access, create an application, choose its scopes, and store the resulting client_id and client_secret. The integration exchanges those credentials for a bearer token; the token’s organization and scopes determine which tenant and operations it can reach.
The official documentation separates permissions by resource and action—for example, load:read, carrier:update, or tender:create. Create one app per automation and grant only the scopes it needs.
Alvys versions its API in the URL and publishes an OpenAPI surface, making it straightforward to generate a typed client for the exact freight workflows Carly will run.
Webhooks turn Alvys changes into work
Alvys has a substantial webhook catalog. Recent additions include load.changed and trip.changed, plus document events for loads, trips, drivers, carriers, trucks, and trailers. A POD upload can carry a short-lived download URL, while change events can optionally include prior values so the receiver sees the delta.
Webhook access is currently enabled by request. Once enabled, configure it under Settings → Connections → Webhooks for each subsidiary. Alvys verifies the HTTPS endpoint before delivering events and signs subsequent payloads. Keep the event ID as the idempotency key because retries and duplicate delivery are normal webhook behavior.
Contact the Customer Success or Implementation Manager for the account to enable webhooks before launching a workflow that depends on real-time delivery.
The official Alvys MCP option
Alvys’s MCP server is first-party and uses the same permissions as the public API. It connects to Claude, Cursor, and other remote-MCP clients at:
https://mcp.prod.alvys.net/mcpInteractive clients use OAuth login. Headless agents can reuse API client credentials. Tools cover loads, trips, drivers, carriers, tracking, documents, and financial operations, making the MCP useful for questions such as “which open loads lack a carrier?” or “show invoice status for these loads.” Production MCP tools currently retrieve data; Carly uses the public API and webhooks when an automation must update records.
What Carly can run around Alvys
Carly uses your Alvys credentials and carries work across the TMS, email, accounting, calendars, and team notifications.
- POD-to-billing agent: a proof of delivery lands, Carly verifies the document set, alerts billing, drafts the invoice handoff, and chases anything missing.
- Dispatch brief agent: before the morning stand-up, compile open loads, uncovered freight, late pickups, missing driver assignments, and the exceptions that need a person.
- Detention agent: start from arrival and departure updates, assemble the timeline and supporting records, and create the recovery task while the evidence is fresh.
- Customer update agent: when a trip status or appointment changes, send the approved update with the load number, new timing, and next checkpoint.
- Carrier onboarding agent: check the packet and authority data, list what is missing, request it, and update operations when the file is complete.
- Settlement review agent: reconcile charges, deductions, carrier pay, and customer pay; route only out-of-tolerance items for approval.
- Document agent: classify BOLs, PODs, rate confirmations, and other uploads, attach them to the right workflow, and maintain the audit trail.
The Alvys API handles production reads and writes, while its official MCP provides a convenient conversational surface. Carly can use both connection paths as parts of the same freight workflow.
Frequently asked questions
Does Alvys have a public API?
Yes. It exposes scoped APIs for freight operations including loads, trips, drivers, carriers, equipment, documents, tenders, tracking, and settlement-related data.
Does Alvys have an official MCP server?
Yes. Alvys operates a first-party remote MCP server for exploring loads, trips, drivers, carriers, tracking, documents, and financial operations. Access is currently granted on request.
Can Alvys webhooks trigger automations?
Yes. Events include load and trip changes, status changes, tenders, and document uploads or deletions. Webhooks are enabled by request and configured per subsidiary.
How do I get Alvys API credentials?
Create an API application under Admin → API Access, assign the required scopes, and use its client ID and secret to obtain OAuth bearer tokens.
What can Carly automate with Alvys?
Carly can coordinate POD collection, billing handoffs, dispatch briefs, customer status updates, detention documentation, carrier onboarding, document filing, and settlement review across Alvys and the team’s communication and accounting tools.
More: Samsara API · Motive API · Fleetio API · What is MCP?
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
