Where should developers start in SignalEDI docs?

Start with account setup and API upload patterns, then review X12 basics, trading partner configuration, webhooks, and billing endpoints linked from the docs hub.

Does documentation cover healthcare and supplier workflows?

Yes. Guides reference healthcare 837/835/270/271 examples and supplier order-to-cash flows with validation and acknowledgement patterns.

How do docs connect to self-serve onboarding?

Docs link to QuickStart, trial, and the in-app setup cockpit so technical and operations teams can move from reading to guided implementation.

What is EDI integration?

Electronic Data Interchange (EDI) is the standard format used by businesses and healthcare organizations to exchange documents like purchase orders, invoices, and insurance claims. EDI integration connects your internal systems to trading partners that require EDI X12 format.

Do I need EDI expertise to use SignalEDI?

No. SignalEDI handles all the EDI complexity on your behalf. You send and receive data in standard formats like JSON or CSV, and SignalEDI translates everything to and from EDI X12 automatically.

How long does trading partner onboarding take?

Certifying with major trading partners (large retailers, healthcare payers) typically takes 6–8 weeks due to their internal intake, testing, and certification processes. That timeline is controlled by the trading partner, not SignalEDI platform setup (which is typically ready in days, not weeks).

Can SignalEDI sync EDI transactions to QuickBooks?

Yes. The ERP Marketplace add-on provides native connectors for QuickBooks Online, Sage, NetSuite, Xero, and more. 850 POs become bills, 810 invoices post to accounts receivable, and 835 remittance advices match to payments — no manual re-keying.

Is there a free trial?

Yes. SignalEDI offers a 30-day free trial with no credit card required. No setup fees, no long-term contracts, and you can cancel anytime.

What HIPAA transaction sets does SignalEDI support?

SignalEDI supports common HIPAA-governed X12 transaction formats including 837P/I/D (medical claims), 835 (remittance), 270/271 (eligibility inquiry/response), 278 (prior authorization request/response), and 277 (claim status). Healthcare workflows can be evaluated on paid plans. Production PHI requires an executed BAA plus the HIPAA/BAA add-on ($199/mo; included on Enterprise).

How is SignalEDI different from a traditional EDI clearinghouse?

Traditional clearinghouses require expensive setup fees ($500–1,500 per partner), long contracts, and EDI expertise. SignalEDI offers transparent all-inclusive pricing, a self-serve dashboard, and a modern API-first interface so you can prepare the work your side controls before partner certification finishes.

Where is my data stored?

Production files and transactions use encrypted AWS services: PostgreSQL on Amazon RDS and private Amazon S3 object storage. Data is encrypted at rest and in transit, with tenant isolation and audited access controls.

How do I cancel my subscription?

Open Dashboard → Subscriptions, scroll to **Leaving SignalEDI? Offboarding**, and choose **Cancel at period end**. You can undo cancellation any time before the billing period ends. You can also use **Manage Billing** in Stripe for payment method updates.

I uploaded an EDI file but it shows FAILED — what do I do?

Click the failed transaction to see the validation error details. Common issues: incorrect ISA/GS IDs (partner not found in your account), missing mandatory segments, or incorrect segment terminators. Fix the file and re-upload. If you need help, email support@signaledi.com with the transaction ID.

Documentation

SignalEDI documentation

API-first EDI docs for onboarding, X12 basics, trading partner setup, billing, REST endpoints, and webhooks — with JSON/CSV intake, instant validation, and real-time visibility.

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.

Start free trial Developer hub

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.

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.

Product principle — mechanized self-serve: SignalEDI is an AI-first company: product, support, onboarding, reliability, and growth are designed so AI and intelligent automation perform as much work for the SMB customer as possible—safely, auditably, and supportively—with humans focused on exceptions, governance, and judgment calls. Onboarding, support, integrations, compliance, billing, and growth must be mechanized. If the product depends on humans for default paths, SignalEDI becomes another legacy vendor. If it depends on automation, it scales like software. Every feature and process change should ask: does this maximize supportive automation and AI-assist for the SMB, and reduce human dependency on the default path?

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, poNumber, line items, and webhook status handling.

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

Validate a sample file →Preview field mapping →

Still have questions?

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

Contact support