Home / Integrations
IntegrationsTMS, API and EDI — what exists today
This page is an availability statement, not a roadmap promise. It lists what a shipper or carrier can use today, what is deliberately not offered, and what an integration request currently gets: a human answer from dispatch.
Portlandia Logistics does not operate a proprietary TMS portal for shippers, does not offer EDI tender/status/invoice transactions today, and does not publish a booking API. The one programmatic surface that is live is the quote API described on /api-docs, authenticated with a shipper API key.
Can I integrate this today?
One line per surface. If a surface is not listed here, it does not exist — the dated per-transaction detail is on the EDI status page, last reviewed November 16, 2026.
| Surface | Status | What you can do today | What it does not do |
|---|---|---|---|
| Quote API v1 | Available now | POST /api/v1/quote returns a planning estimate with mileage, transit and basis. | No booking, tender or invoice object. Authenticated with a shipper API key. |
| Rate index API | Available now | GET /api/rate-index returns the same stored-quote aggregates as the page. No key required. | Aggregates only; medians withheld below n=5; no shipper identity or quote numbers. |
| OpenAPI 3.1 description | Available now | /openapi.json describes the public quote, rate-index and agency endpoints, fields and errors. | Covers those endpoints only — there is no EDI or webhook path in it. |
| Hosted record links | Available now | Tokenized quote, load and invoice pages can be linked from email, a wiki or an internal tool. | The link is the integration; documents stay behind the token, not a public URL. |
| CSV extracts | On request | Dispatch emails an export of quote or load records for a date range and named fields. | No self-serve export portal and no scheduled feed. |
| EDI 204 / 990 / 214 / 210 | Not offered | Nothing to integrate today. | No EDI VAN, AS2 or SFTP connection. The dated statement is on /edi-status. |
| Native TMS connectors | Not offered | None pre-built for MercuryGate, Turvo, McLeod, Oracle OTM or SAP TM. | Custom integration would be scoped and priced before work starts. |
| Booking / tender API | Not offered | Bookings happen on the hosted quote page or with dispatch. | No endpoint creates a load, accepts a tender or issues an invoice. |
| Tracking webhook / status subscription | Not offered | None. | Status is read from the tracking page or the tokenized portal record; no push or subscription exists. |
The same facts in machine-readable form: /openapi.json for the live endpoints, and /edi-status for the EDI sets that do not exist yet.
Available, on request and not offered
Available now
Quote API (REST)
Server-to-server JSON quotes for a lane, using a shipper API key issued from the account page. Returns mileage, transit days and the planning range with the basis. No booking, no tenders, no invoice objects.
Available now
Hosted record links
Every quote, load and invoice has a tokenized hosted page. You can link a shipper record into an internal tool, email or wiki without an API — the link is the integration.
On request
CSV extracts
Dispatch can export quote and load records as CSV for a period and email them. Ask with the date range and the fields you need; there is no self-serve export portal.
Not offered
EDI (204 / 990 / 214 / 210)
No EDI VAN, AS2 or SFTP endpoint is connected. We will not claim an EDI capability we cannot transact. If EDI is a hard requirement, we will say so before you tender.
Not offered
Native TMS connectors
No pre-built connectors for MercuryGate, Turvo, McLeod, Oracle OTM or SAP TM. A TMS integration would be a custom project, scoped and priced before any work starts.
Not offered
Booking / tender API
Bookings are made on the hosted quote page or with dispatch. There is no unauthenticated booking endpoint and no API that creates loads or invoices.
How an integration request is handled
- Send the requirementWhat system, which direction (quote only, tender, status, invoice), and the volume. Email [email protected] with "integration" in the subject.
- Written answer within two business daysEither the request is served by the quote API or hosted links, or it is out of scope today. We do not sell a roadmap.
- Scoped project if it proceedsCustom work is scoped, priced and agreed in writing before a line of code or a credential is shared.
Integration questions
What is live, what is not, and what a booking requirement actually gets today. Visible answers match the FAQ markup on this page.
Is the quote API actually live?
Yes. POST /api/v1/quote is a production endpoint, authenticated with a shipper API key issued from the account page. It returns the same planning range the hosted form shows — mileage, transit days and the calculation basis — and nothing else.
Do you support EDI 204, 990, 214 or 210 today?
No. There is no EDI 204 load tender, no 990 response, no 214 status message and no 210 invoice, and no EDI VAN, AS2 or SFTP connection is configured. The dated per-transaction statement is on /edi-status; if EDI is a hard requirement, we will say so before you tender rather than after.
Is there a booking or tender API?
No. There is no endpoint that creates a load, accepts a tender or issues an invoice. Bookings are made on the hosted quote page or with dispatch, and the rate confirmation is issued in writing.
Can you integrate with our TMS?
There are no pre-built connectors for MercuryGate, Turvo, McLeod, Oracle OTM or SAP TM. A TMS integration would be a custom project — scoped, priced and agreed in writing before any credential or code is shared. The quote API and hosted links cover most quote-only needs today.
Need a requirement answered in writing? Email [email protected] with the system, direction and transaction set.
Need a quote in your own system?
The quote API is live today and takes a shipper API key. The docs show the request, the response and the error codes; the EDI status page shows what is deliberately not offered.