Platform Limits
These are the size and rate limits that apply when processing data through Tediware.
Payload Size
EDI files are limited to 1 MB each. A typical document stays far below this: 1 MB fits several thousand line items. If you expect larger files, contact us and we can raise the limit for your account.
Transformation Execution
JSONata transformations have a maximum execution time of 5 seconds. An expression that exceeds the limit is terminated and returns an error. If a transformation times out, simplify the expression or reduce the input data size.
Schema Validation
JSON schema validation has a maximum execution time of 10 seconds. Validation that exceeds the limit is terminated and returns an error.
API Rate Limits
Platform API requests are rate-limited per API key:
- Read endpoints (fetching results, artifacts, and the feed): 2,400 requests per minute.
- Write endpoints (submitting EDI or JSON): 600 requests per minute.
- Resend or redeliver: 10 requests per minute, shared between the two. Each accepted resend puts a document on a trading partner’s wire, and each redelivery reaches your own endpoint again, so this one is deliberately tight.
MCP tool calls count against these same limits rather than a separate allowance, matched to the work each tool does: x12_releases spends the X12 reference allowance, edi_inspect spends the inspection allowance, partner_send and partner_receive spend the write allowance, and the rest spend the read allowance.
When you exceed a limit, the API responds with 429 and a Retry-After header telling you how many seconds to wait. The API reference Errors page covers the full response format and how to handle it.
If you need higher rate limits, contact us and we’ll be happy to help.