Frequently asked questions.

Vibe EDI is a B2B EDI platform for X12 and EDIFACT over AS2. Each customer gets a dedicated endpoint, a web console, a REST API and webhooks into their ERP.

No. Each customer runs on a dedicated single-tenant stack with its own endpoint, database and AS2 identity. Your documents never share a database with another customer.

ANSI X12, versions 4010 through 6020 and later, and EDIFACT. Both are supported inbound and outbound over the same AS2 connection.

AS2 and SFTP. AS2 is signed and encrypted, with MDN receipts, and SFTP uses SSH-key authentication. Partners that only offer a plaintext AS2 port are supported because the payload is encrypted before it leaves.

No. Your partners send directly to your AS2 endpoint. You give them the URL, certificate and IDs shown in the console.

Yes. You keep your partners and your EDI documents; only the connection changes. Each partner points their AS2 connection at your new endpoint, and you run test traffic with them on the test stream before you switch that partner live. You can move partners one at a time while your old provider keeps carrying the rest.

Usually days, not months. Your endpoint is provisioned when you sign up. Then you add the partner, generate the map with Vibe Mapping, exchange test documents on the test stream and flip the partner live. Most of the time goes to scheduling the test with your partner.

Post your business JSON to the REST API for a partner and transaction set. The platform maps it, builds the envelope, assigns control numbers and sends it. You get tracking ids back right away.

Inbound EDI is decoded, mapped to your JSON and delivered to your webhook. Webhooks authenticate with an API key or Basic credentials you define.

Yes. Every transaction has input and output artifact URLs, available through the REST API with your API key.

With Vibe Mapping, which is included. Traditional EDI mapping means a specialist hand-builds each map in a dedicated tool, or a provider builds it for you and you wait on them for every change. With Vibe Mapping, you describe the mapping in plain English and add sample documents. It writes a working map in seconds and runs it against your samples, so you can check the output before you ship. When a partner changes a requirement, describe the change and Vibe Mapping updates the map. You can see, edit and own every map in the console.

Yes. An agreement can bind a specific map to each transaction set. A missing bound map stops the message with an error rather than falling back silently.

It appears in the ledger with a failure code and the full error. Fix the cause and retrigger it in one click. Your ERP can also receive a failure event.

Yes. The Vibe Agent is an optional assistant in the console. It can look up your trading partners, agreements and certificates, explain how they are set up, and help troubleshoot a failed message. It can also propose changes to partner and agreement configuration, which take effect only after they are approved.

Yes. The Network access panel holds an IP allowlist for the REST API. AS2 traffic stays authenticated by certificates.

Yes. You can install your own AS2 identity from the Certificates panel. The key is stored only in your own stack.

Yes. Your database and configuration are backed up daily with continuous log archiving. Backups are encrypted before they leave your stack.

Each customer runs on a dedicated single-tenant stack. AS2 documents are signed and encrypted in transit, every other connection uses HTTPS, disks are encrypted at rest, and backups are encrypted before they are stored. Failed sends retry automatically, and anything that still fails stays in the ledger to replay. Mapped JSON is kept for 90 days; the raw EDI is kept as your audit record for as long as you have an account. A SOC 2 audit is in progress.