EnergyEDI receives incoming HTTP post requests from various trading partners. It parses and validates HTTP parameters set in the request based on NAESB 1.7 standards. EnergyEDI sends appropriate EDI errors back as part of the response. Encrypted EDI Documents are received as part of HTTP Post requests. Encrypted EDI Document will be saved in designated IN directory. This document will then be decrypted using the private key and parsed. Data will be retrieved from X12 datasets and exported in various formats such as XLS, XML and CSV. This can be imported in the backend process such as EBB for further processing. Responses generated from EBB will be translated back to X12 datasets, PGP encrypted using trading partner’s public key. Appropriate parameters will be set on http response and encrypted file will be transmitted back to trading partner.

EnergyEDI website receives incoming http post requests from various trading partners. It parses and validates http parameters set in the request and sends appropriate EDI errors back as part of the response. EDI Document will be saved in designated directory. This document will be decrypted using private key and parsed. Data will be retrieved from X12 datasets and exported in various formats such as XLS, XML and CSV. This can be sent to TSP’s EBB for further processing. Documents are received as part of HTTP Post requests. Responses generated from EBB will be sent to EnergyEDI website URL. These are translated back to X12 datasets, pgp encrypted using trading partner’s public key. Appropriate parameters will be set on http response and encrypted file will be transmitted back to trading partner.