Orderful EDI API
★ Only Publicly Available OpenAPI DocumentE CommerceShipping LogisticsapiKey14 EndpointsREST
For Agents
Send and receive EDI transactions, track delivery status, and convert between EDI and JSON formats across retail and supply-chain trading partners.
Use for: I need to send an 850 purchase order to a trading partner, Check whether an outbound EDI transaction was approved by the receiver, Retrieve the raw EDI message for a given transaction id, List all inbound transactions waiting in my Orderful inbox
Not supported: Does not handle payment settlement, carrier rate shopping, or warehouse management — use for EDI document exchange and trading partner workflows only.
Jentic publishes the only available OpenAPI specification for Orderful EDI API, keeping it validated and agent-ready. Orderful is a cloud-based EDI platform that connects retailers, suppliers, and 3PLs through a single API for exchanging trading-partner documents such as purchase orders, ASNs, invoices, and acknowledgments. The API exposes 14 endpoints covering transaction lifecycle, delivery tracking, format conversion between EDI X12 and JSON, label generation, and trading partner relationships. It removes the need to operate VANs or AS2 connections by handling routing, validation, and acknowledgments centrally.
Install Jentic One Beta
Connect the Orderful EDI API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Orderful EDI API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Orderful EDI API.
Submit outbound EDI transactions like 850 purchase orders or 856 ASNs to trading partners via POST /transactions
Track delivery state of an EDI transaction and confirm partner-side approval through GET /transactions/{id}/delivery
Send 997 functional acknowledgments back to trading partners using POST /transactions/{id}/acknowledgment
Pull the inbox of inbound transactions awaiting processing through GET /inbox
Convert EDI X12 payloads into Orderful JSON and back via POST /convert without running a separate translator
Generate UCC-128 shipping labels tied to an outbound shipment with POST /labels
List active trading partner relationships and supported transaction sets through GET /relationships
Use Cases
Patterns agents use Orderful EDI API for, with concrete tasks.
★ Retail Drop-Ship EDI Onboarding
Suppliers selling through Walmart, Target, or Amazon Vendor Central can use Orderful to exchange 850 purchase orders, 855 acknowledgments, 856 ASNs, and 810 invoices without standing up their own EDI translator or VAN. Orderful handles partner mapping and acknowledgment workflows, and the API lets engineering teams plug EDI directly into ERP or OMS systems.
Submit a POST /transactions with an 856 ASN payload referencing PO 4501234567, then poll GET /transactions/{id}/delivery until status becomes approved.
EDI to JSON Format Conversion
Teams that store data as JSON in their warehouse or order management system can call POST /convert to translate inbound X12 documents into structured JSON, and outbound JSON back into compliant X12. This avoids embedding an X12 parser into application code and keeps validation rules in Orderful.
POST a raw X12 850 string to /convert and parse the returned JSON to extract line items and ship-to address.
Functional Acknowledgment Automation
Trading partners require timely 997 functional acknowledgments confirming receipt of EDI documents. Agents can listen for inbound transactions through GET /inbox, validate them, and POST /transactions/{id}/acknowledgment to send back the 997 within the contractually required SLA window, avoiding chargebacks.
Iterate over GET /inbox results and POST /transactions/{id}/acknowledgment with status accepted for each successfully validated transaction.
Agent-Driven EDI Operations via Jentic
AI agents that handle order operations can send and reconcile EDI documents through Jentic without learning the X12 standard. Jentic exposes Orderful operations by intent (send purchase order, check delivery, acknowledge receipt) and isolates the API key in the vault.
Use Jentic to search 'send an EDI purchase order to a trading partner', load the schema for POST /transactions, and execute with a generated 850 payload.
Key Endpoints
14 endpoints — jentic publishes the only available openapi specification for orderful edi api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/transactions
Submit an outbound EDI transaction
GET
/transactions
List transactions with filters
GET
/transactions/{id}/delivery
Check delivery status of a transaction
POST
/transactions/{id}/acknowledgment
Send a 997 functional acknowledgment
GET
/inbox
List inbound transactions awaiting processing
POST
/convert
Convert between X12 EDI and JSON
POST
/labels
Generate UCC-128 shipping labels
GET
/relationships
List trading partner relationships
POST
/transactions
Submit an outbound EDI transaction
GET
/transactions
List transactions with filters
GET
/transactions/{id}/delivery
Check delivery status of a transaction
POST
/transactions/{id}/acknowledgment
Send a 997 functional acknowledgment
GET
/inbox
List inbound transactions awaiting processing
POST
/convert
Convert between X12 EDI and JSON
POST
/labels
Generate UCC-128 shipping labels
GET
/relationships
List trading partner relationships
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Orderful API keys are stored encrypted in the Jentic vault. Agents receive scoped execution access — the raw key never enters the agent's context or model prompt.
Intent-based discovery
Agents search by intent (e.g., 'send an EDI purchase order') and Jentic returns the matching Orderful operation with its input schema, so the agent can call POST /transactions without parsing X12 documentation.
Time to first call
Direct Orderful integration: 1-2 weeks for auth, transaction lifecycle, and acknowledgment handling. Through Jentic: under an hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Orderful EDI API through Jentic.
Why is there no official OpenAPI spec for Orderful EDI API?
Orderful does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Orderful EDI API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Orderful EDI API use?
The API uses an API key passed in a request header (ApiKeyAuth scheme). Through Jentic, the key is stored encrypted in the vault and never enters the agent's context — Jentic injects it at execution time.
Can I send an 856 ASN through the Orderful EDI API?
Yes. POST /transactions with the ASN payload identified by transaction set 856 and the relevant trading partner relationship. Status is then tracked through GET /transactions/{id}/delivery.
What are the rate limits for the Orderful EDI API?
The OpenAPI spec does not declare numeric rate limits. Orderful's documentation notes throttling on bulk transaction submission — check docs.orderful.com for current per-account limits before running large batches.
How do I convert X12 EDI to JSON through Jentic?
Search Jentic for 'convert EDI to JSON', load the schema for POST /convert, and execute with the raw X12 string. The response contains the structured JSON representation Orderful uses internally.
Does the Orderful EDI API generate shipping labels?
Yes. POST /labels generates UCC-128 carton labels tied to an outbound transaction. The label is returned as a printable artifact you can attach to your fulfillment workflow.
GET STARTED