Skip to main content

Documentation

Onboard partners faster with API docs, X12 guides, and setup checklists

Getting started, EDI fundamentals, partner setup, billing, API reference, and FAQ — linked to developer tools, trust artifacts, and free validation sandboxes.

Public documentation coverage

This public docs hub covers the standard SMB evaluation path: account setup, dashboard navigation, EDI basics, file processing, trading-partner setup, billing, API authentication, REST endpoints, code samples, webhooks, rate limits, and production readiness.

Contact support when your partner mandate needs contract-specific trust artifacts, BAA/DPA review, or managed onboarding help.

2026-09 white paper

Enterprise document API onboarding

Validate the customer side in Lab, certify the exact partner route in Certification, then promote the same contract through governed Production authority.

2026-09 white paper

Mapping and payload contracts

Compare raw, structured, typed document, and approved mapped views; discover capability; and certify deterministic edge cases.

Send JSON, CSV, or EDI samples; validate instantly; route X12 in real time; and connect partner workflows without per-document fee surprises. For a copy-paste first upload, start with the Developer QuickStart. Use the docs sidebar to open any topic page.

AI documentation assistant

Ask docs questions by workflow, error, or API example

Suggested queries help operators jump from an X12 error to a fix, generate example API calls, or understand how to send healthcare and supplier documents without waiting for support.

Autocomplete: “837 claim validation”, “999 error”, “850 API payload”, “QuickBooks 810 invoice”
Explain this error

IK3*NM1*2310B failed

NM1 provider loop is missing a required identifier. Add qualifier XX and the provider NPI before resubmitting.

Validate an 837

validate an 837 claim

Validate a complete native X12 interchange or send 837 claims through the JSON outbound endpoint, then monitor 999 and 277 acknowledgements.

Generate API example

node example for 850

Generate a Node fetch call with partnerId, environment, purchaseOrderNumber, line items, an idempotency key, and receipt handling.

curl -X POST https://api.signaledi.com/v1/validate \
  -H "Authorization: Bearer $SIGNALEDI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"content":"ISA*... complete native X12 837 interchange ...~IEA*...~"}'

Still have questions?

Our support team typically responds within a few hours during business hours.

Contact support

© 2026 SignalEDI Inc. All rights reserved.