Home / Integrations / EDI status
EDI & visibility statusEDI, API and tracking: what exists today, and what does not
Most integration pages describe a roadmap as if it were a product. This one is a status statement: the visibility and programmatic surfaces that work today, the EDI transactions that do not exist, and what would have to be true before each one is offered. No completion dates are promised and no capability is claimed that cannot be transacted.
Last reviewed . This date is changed only after the claims below are re-checked against the shipped code; it is not refreshed by a deploy.
There is no EDI 204 load tender, no 990 response, no 214 status message and no 210 invoice. There is no EDI VAN, AS2 or SFTP connection, no API push into a shipper or carrier TMS, and no public tracking webhook. The quote API is live and returns planning estimates only.
What exists today
These four surfaces are the complete list of visibility and programmatic access that exists today. Everything not listed on this page is not offered.
| Surface | What it does |
|---|---|
Tracking page/tracking | Status-only lookup by load, quote or invoice number. Rate confirmation, invoice and POD stay behind the tokenized record link, not the public lookup. |
Quote API v1/api-docs | Authenticated server-to-server POST /api/v1/quote returns planning mileage, transit days and the estimate range with its calculation basis. It does not create quotes, tenders, bookings or invoices. |
Rate index/rate-index | Aggregates of the stored quote requests this site returned, with sample size, window and basis shown; medians are withheld below n=5. The same aggregates are served by GET /api/rate-index with no key. |
Authenticated portal/portal | Token-based shipper and carrier portal for saved records, quotes, loads and invoices. Login is required and the portal is not a public tracking surface. |
The machine-readable description of the public endpoints is at /openapi.json. It covers the quote and rate-index endpoints only; there is no EDI or webhook path in it.
What does not exist today
This table is the negative statement, in full. If a capability is not in the table above, it is in this one.
| Capability | Status | Detail |
|---|---|---|
| EDI 204 — load tender | Not available today | No EDI tender set is accepted. Loads are not tendered electronically today. |
| EDI 990 — tender response | Not available today | No 990 response is sent, because no 204 tender is exchanged. |
| EDI 214 — shipment status | Not available today | No 214 status message is generated. Status lives on the tracking page and portal records. |
| EDI 210 — freight invoice | Not available today | No 210 invoice is transmitted. Invoices are issued through the hosted invoice path. |
| EDI transport (VAN, AS2 or SFTP) | Not available today | No VAN, AS2 or SFTP connection is configured with any trading partner. |
| API push to a shipper or carrier TMS | Not available today | No outbound API writes load or status data into a third-party TMS. |
| Public tracking webhook or status subscription | Not available today | No webhook URL is published and no status subscription is offered. |
| Booking or tender API | Not available today | No endpoint creates a load, accepts a tender or issues an invoice. |
No connector is named as available until it can be transacted. If a customer requires one of these to onboard, the requirement is answered honestly and in writing rather than promised.
Roadmap: what would need to be true
Each EDI transaction set and the status webhook require integration work before they can be offered. This table states the prerequisite for each; it deliberately carries no dates and no service-level promises.
| Capability | Status today | What would need to be true to offer it |
|---|---|---|
| EDI 204 — load tender | Not available today | A carrier or TMS integration plus customer onboarding: a trading-partner agreement, an EDI transport (VAN, AS2 or SFTP), a 204 map for the shipper and receiving carrier, and a dispatch process that owns tenders, rejections and re-tenders. |
| EDI 990 — tender response | Not available today | The same carrier and transport work as the 204. A 990 has nothing to answer until tenders are exchanged electronically, so it ships with the 204 integration rather than before it. |
| EDI 214 — shipment status | Not available today | A carrier status feed or TMS integration that emits status events, an event store that keeps them with timestamps, a 214 map for the customer, and a monitoring process for missed or stale events. |
| EDI 210 — freight invoice | Not available today | Billing onboarding with the customer and an invoice-to-210 map on the same transport as the other sets. The transmitted total must reconcile to the rate confirmation before any 210 is sent. |
| API webhook — outbound status push | Not available today | An outbound event store with customer endpoint registration, authentication, retry and ordering rules. That subscriber system does not exist today, so no webhook endpoint or delivery schedule is published. |
No completion date, delivery window or service-level target is published for any row. If a date is ever committed, it will be a written agreement with a named customer, not a line on this page.
Questions
Does Portlandia Logistics support EDI 204 or EDI 214 today?
No. There is no EDI 204 load tender, no 990 response, no 214 status message and no 210 invoice today. No EDI VAN, AS2 or SFTP connection is in place, so no EDI transaction set is claimed or accepted.
Can Portlandia Logistics push load status into our TMS by API?
No. There is no API push to a shipper or carrier TMS and no public tracking webhook. The quote API returns planning estimates only, and load status is read from the hosted tracking page or the tokenized portal record.
What can we use today for status, tracking and rates?
The tracking page, the tokenized portal records, the public rate index and the quote API with its OpenAPI description. Those are the only visibility and programmatic surfaces that exist today, and each is linked from this page.
What would need to be true to offer EDI 204, 990, 214 and 210?
A carrier or TMS integration plus customer onboarding: a trading-partner agreement, an EDI transport such as VAN, AS2 or SFTP, message maps for each transaction set, and a dispatch process that owns tenders, responses, status events and invoices. None of that exists today, so no date is promised.
Related surfaces
Integrations availability statement
Public tracking page
Quote API documentation
OpenAPI description
How to get status today
Track a load or quote on the tracking page, or open the tokenized record from the confirmation email. Public lookups return status only; documents need the private record link.
No email, SMS or webhook status subscription is offered today.
Integration requirement?
Send the system, the direction and the transaction set. The answer states what exists, not what might.
Email the deskQuote first, integrate second
The quote API and the hosted quote form use the same estimate model. EDI and status webhooks are not available today.