EDI API is organized around REST. Our API has predictable resource-oriented URLs, accepts either multipart/form-data or JSON-encoded/XML-encoded request bodies, returns either JSON-encoded/XML-encoded or application/octet-stream responses, and uses standard HTTP response codes, authentication, and verbs.
When we make backwards-incompatible changes to the API, we release new versions. The current version is v1.
The base URL for the current version 1 is:
The API reference is depicted using Swagger UI:
The API reference lists all the operations and request\response models. Each transaction is represented as EdiMessage which is the base class for all the derivative transaction models.
Client SDKs can be downloaded from our Swagger Hub - EdiFabric EDI API Swagger Hub
The particular EDI transaction models are also depicted using Swagger UI:
Explore the API reference for full list of the supported operations, parameters and models.
The following endpoints are available:
Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.
For evaluation purposes use the following API key:
The free plan is restricted for single client IP address to only 10 calls every minute, with a total of 500 calls and 100 MB of bandwidth per month.