Your app. Our EDI API.
Parse and validate EDI, send supported outbound documents, and track acknowledgements. Configure your partner connection and environment before exchanging documents.
Explore the API reference →SignalEDI developers · EDI API, SDKs & MCP
Old protocols.
New tricks.
JSON in. Validated X12 out. Give your app an EDI API, keep your stack, and get back to the part you actually wanted to build.
5,000 calls / month free. Then $0.0015 / call.
Explore API usage plans
01 / From your app to X12Example request + response
example-request.sh
$ curl -X POST https://api.signaledi.com/v1/documents/outbound \ -H "Authorization: Bearer sk_sandbox_8f2a" \ -H "Content-Type: application/json" \ -d '{ "partnerId": "your-partner-id", "documentTypeCode": "850", "payload": { "purchaseOrderNumber": "PO-1042", "lines": [{ "sku": "SKU-100", "quantity": 24, "unitPrice": 12.5 }] } }' → { "ok": true, "documentId": "doc_8f2", "status": "queued" }
Synthetic example. Partner exchange requires a configured connection, testing, and the appropriate environment.
REST API v1 / bring your stackTypeScript / use the SDKMCP v0.4 / synthetic evaluation
Choose your entry point
Bring your stack.
We brought the EDI.
SignalEDI gives developers an EDI API for parsing, validating, and exchanging business documents. Embed B2B integration in your application, connect through REST or SDKs, and evaluate agent workflows with MCP.
Less glue. More code.
Use the TypeScript SDK or start from curl, Node.js, Python, and Go examples. Follow the quickstart and wire EDI events into your application.
Find examples for your stack →Let your agent nerd out.
Give compatible agent tools structured X12 guidance through the free MCP package. Public v0.4 is for synthetic evaluation only; hardened v0.5 remains pending release verification.
Review MCP capabilities and installation →Embedding EDI in a SaaS product or platform? Explore the platform integration path. For healthcare integration requirements, Rail by SignalEDI offers a design-partner path with synthetic evaluation; production routing and packaging remain roadmap.
Less slide deck. More request body.
Here's the interesting bit.
An outbound purchase order, in your language. These examples use synthetic data and a placeholder key; your partner connection supplies the real routing.
curl -X POST https://api.signaledi.com/v1/documents/outbound \
-H "Authorization: Bearer sk_sandbox_8f2a" \
-H "Content-Type: application/json" \
-d '{ "partnerId": "your-partner-id", "documentTypeCode": "850",
"payload": { "purchaseOrderNumber": "PO-1042",
"lines": [{ "sku": "SKU-100", "quantity": 24, "unitPrice": 12.5 }] } }'
# → { "ok": true, "documentId": "doc_8f2", "status": "queued" }Events you can work with.
Connect supported webhook events to your workflow. Follow the guide for subscriptions and signed delivery handling.
Give the edge cases a turn.
Try synthetic files and rejection scenarios in the EDI test lab. See validation findings before configuring your partner exchange.
Your agent can read along.
Explore X12 guidance through MCP. Local guidance is not a billable API call. Check the package's version-specific capabilities before installing.
Developer API usage plans
First call. Then your next idea.
The Free tier includes 5,000 calls / month; pay-as-you-go usage beyond it is $0.0015 / call. A billable call is one parse or one validate request. Scale offers committed-volume terms. Direct accounts and Vercel Connectable installs use SignalEDI Stripe billing.
- 01 / KEY
Make it yours.
Create a developer account without a credit card. Get a platform-scoped API key, keep it private, and start with synthetic data.
Get a developer API key → - 02 / REQUEST
Meet your first response.
Explore the public playground, then make an authenticated parse or validate call. A playground preview does not activate a partner connection.
Open the API playground → - 03 / REPEAT
Keep an eye on the meter.
Manage keys, inspect usage, and review billing options in the console. Add pay-as-you-go when you're ready to use more than the free allowance.
Open the developer console →
Need to run your company's B2B integration and trading-partner operations? Explore SignalEDI for businesses and core EDI plans. Core subscriptions and their document allowances are separate from this developer API usage meter.
Pricing crosswalk
SMB plans vs developer API usage
Teams pick a published monthly plan. Developers start with a monthly call allotment, then pay per call. Numbers come from the same catalogs as checkout and the developer register.
| Audience | Model | Included | After the included amount |
|---|---|---|---|
| SMB teams | Flat monthly plans | Published — $99/$199/$999/$1999 | No standard per-document toll; finite plans pause at the included allowance and paid overage is not currently available SMB pricing |
| Developers | Usage after a free monthly allotment | 5,000 calls / month | $0.0015 / call Developer API pricing |
SignalEDI for Vercel
Marketplace integration
Vercel Marketplace · Connectable
Your Vercel project. Now speaking EDI.
Install the public SignalEDI integration, choose your projects and environment targets, and get project-scoped API and webhook credentials provisioned for your app.
Install flow
- 01Select projects and environment targets.
- 02Provision a workspace and scoped credentials.
- 03Parse and validate; configure a partner connection for exchange.
One request path
Vercel appSignalEDI APIEDI partner
Partner exchange requires configuration and testing. Your app keeps control of the workflow.
SignalEDI marketplace lineup
Vercel
Connectable install with project-scoped credentials.
Usage plan · billed by SignalEDI
Open listing ↗
Shopify
EDI workflows for storefront, fulfillment, and partner operations.
Marketplace pricing · announced at launch
Intuit
QuickBooks-connected EDI flows with reviewable accounting handoffs.
Marketplace pricing · announced at launch
Oracle NetSuite
NetSuite-connected EDI flows for orders, fulfillment, invoices, and acknowledgments.
Oracle Cloud Marketplace · live today · version 0.2.0
Oracle Cloud Marketplace is live today. NetSuite SuiteApp Marketplace is a separate planned expansion. Shopify and Intuit remain roadmap destinations until their marketplace submissions and approvals are complete.
Permission to poke around
Got a weird EDI file?
Give it a test run.
Paste or upload a synthetic X12 sample. The public EDI test lab runs production validators and a partner simulator — and will not call that a certification.
A few things before you build
Developer API questions.
What can developers build with SignalEDI?
Developers can add EDI parsing, validation, document exchange, and acknowledgement handling to applications and platform integrations. Start with synthetic examples, then configure the required partner connection and environment before sending documents. Partner testing and production approval are separate steps.
How do developer API usage plans work?
The developer Free tier includes 5,000 calls / month. A billable call is one parse or one validate request; pay-as-you-go usage beyond the allowance is $0.0015 / call. Scale offers committed-volume terms. These usage plans are separate from core business EDI subscriptions and their document allowances.
Can I use REST, SDKs, and MCP with SignalEDI?
Yes, with different release boundaries. REST and SDKs connect your application to the hosted API. The free MCP package connects compatible agent tools; public v0.4 is for synthetic evaluation only, and hardened v0.5 remains pending release verification. Local MCP guidance is not a billable API call.
How do I start as a developer?
Create a developer account without a credit card, obtain your platform-scoped API key, and use synthetic data for your first successful parse or validate call. Continue in the developer console to manage keys, view usage, and review available billing options. Vercel Connectable installs use SignalEDI's direct Stripe billing.