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

edi-214 Transactions API

X12 transaction set management

edi-214 Transactions API is one of 5 APIs that Edi 214 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

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

Requests are made against 2 base URLs: https://api.stedi.com/2024-01-01, https://edi-gateway.logistics-platform.example.com/api.

2 operations 2 paths 9 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://edi-gateway.logistics-platform.example.com/api
Authentication
API Key
Resource Areas
1

Authentication & Security 1

edi-214 Transactions API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (apiKey). By default, every request must be authenticated.

  • apiKey — API key in format "Key {yourapikey}" for Stedi platform access

Paths & Operations 2

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

Transactions 2

X12 transaction set management

GET
/transactions
List EDI 214 transactions
listTransactions 4 params → 200
GET
/transactions/{transactionId}
Get EDI 214 transaction details
getTransaction 1 param → 200404

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Edi214Document (7 properties), Ms1Segment (7 properties), At7Segment (7 properties), LxLoop (5 properties). Each schema is shown below with its type and property counts.

Q2Segment
object
Q2 - Status Details (Weight, quantity, lading details)
4 properties
Edi214Document
object
Parsed representation of an X12 EDI 214 transaction set
7 properties
B10Segment
object
B10 - Beginning Segment for Transportation Carrier Shipment Status Message
4 properties
TransactionList
object
2 properties
Ms1Segment
object
MS1 - Equipment, Shipment, or Real Property Location
7 properties
At7Segment
object
AT7 - Shipment Status Details segment
7 properties
LxLoop
object
LX detail loop containing status events for a shipment segment
5 properties
Error
object
3 properties
Ms2Segment
object
MS2 - Equipment or Container Owner and Type
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

edi-214-transactions-api-openapi.yml Raw ↑

Other APIs Edi 214 publishes across the network.

Stedi EDI API (X12 214 Support)
Flexport EDI API (214 Air Shipment Status)
edi-214 EDI Processing API
edi-214 Shipment Status API
Where this information came from

This is an independent, third-party profile of edi-214 Transactions 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.