Developer ToolsFree calculatorPDF, Excel, Word exportInfor ION

Infor OS ION API and API Flow Payload and Timeout Calculator

This calculator sizes batches for calls through the Infor ION API Gateway and ION API Flows so each call stays inside the documented time-out and payload limits. Enter record size, server time per record and your limits to get a safe records-per-call figure and total run time.

Your numbers

Total records to move

records

Size of one record in JSON

bytes

Measure a real response and divide by its record count

Records per call

500 records

Payload limit per call

Infor pages document 3 or 5 MB per API Flow task and 5 or 10 MB per flow; enter the value that applies to you

Gateway target time-out

seconds

Target timeout is configured between 60 and 300 seconds; API Flows are capped by the 5-minute global gateway time-out

Measured server time per record

Fixed overhead per call

Token check, network round trip, connection setup

Your allowed calls per minute

calls/min

Your own throttle or agreed limit

Your results

Total run time

17.3 min

The larger of sequential call time and the time your calls-per-minute limit allows

Safe records per call (30% headroom)

2,080

Smallest of the payload cap and the count that finishes within 70% of the time-out

Payload per call (MB)

0.7153

Max records per call by payload limit

2,097

Call duration (seconds)

10.4

Call fits time-out and payload limit (1 = yes, 0 = no)

Calls needed

100

Limits are as documented by Infor at time of writing and can change by release and component. Server time per record must be measured on your tenant; this is a planning estimate, not a guarantee.

Save results:

Call duration (s) and payload (MB) vs records per call

Sweeps Records per call from 100 to 5000, holding your other inputs fixed.

Get your batch design reviewed

Send us your record counts, measured timings and the APIs you call and we will review batch size, retries and token handling.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

Documented limits behind the inputs

The ION Desk guide (Infor OS 2026.x) says an API Flow's total duration must be under the global gateway time-out of 5 minutes, that asynchronous requests can run up to 2 hours, and that each individual task must finish in under 5 minutes. Payload limits are stated differently on two pages: 'Creating and using API flows' gives under 10 MB per flow and 5 MB per task, while 'Error handling' gives under 5 MB per flow and 3 MB per task. That is why the payload limit is an input defaulting to the lower 3 MB. The API Gateway documentation sets the configurable target time-out for an API between 60,000 and 300,000 ms. API Flows accept JSON request and response bodies only.

API Flow: under 5 minutes end to end (synchronous)
Asynchronous requests: up to 2 hours
Per task: under 5 minutes; payload 3 to 5 MB depending on page
Target time-out: 60 to 300 seconds

Formulas

Payload per call in MB is records per call times bytes per record divided by 1,048,576. The payload cap is the floor of the limit in bytes divided by bytes per record. Call duration in seconds is fixed overhead plus records per call times milliseconds per record, divided by 1,000. Calls needed is the total records divided by records per call, rounded up. Total run time is the larger of calls times duration (calls made one after another) and calls divided by calls allowed per minute. The safe batch is the smaller of the payload cap and the number of records that finish within 70% of the time-out after overhead. The 30% headroom is a rule of thumb for slow periods, not an Infor figure.

Worked example

With 50,000 records of 1,500 bytes, 20 ms per record, 400 ms overhead, a 60-second time-out and a 3 MB limit: 500 records per call is 0.72 MB and takes 10.4 seconds, so it fits. The payload cap is 2,097 records; the time cap is floor((42,000 - 400) / 20) = 2,080 records, so the safe batch is 2,080. At 500 per call you need 100 calls, about 17.3 minutes sequentially. Moving to 2,000 per call cuts it to 25 calls of 40.4 seconds each, about 16.8 minutes, with fewer requests to throttle. The chart shows where duration crosses the time-out and payload crosses the limit.

Common mistakes

Measuring server time on a quiet test tenant and applying it to month-end production. Forgetting that JSON grows when characters are escaped or fields are added in a later release. Counting the time-out per API step but forgetting that an API Flow's total duration must also be under 5 minutes, so five 70-second steps fail. Retrying failed calls immediately and multiplying load. Ignoring that requests need a valid token; refresh it before it expires during long runs. Not checking the Infor OS service limits documentation for throttling that applies to your tenant.

Frequently Asked Questions

What are the Infor OS service limits for API Flows?

Infor documents a 5-minute global gateway time-out for a synchronous flow, up to 2 hours for asynchronous requests, under 5 minutes per task, and payload limits given as 10 MB per flow and 5 MB per task on one page and 5 MB and 3 MB on another. Check the current release notes.

What is the ION API Gateway time-out?

The target time-out element in the API Gateway is configurable between 60,000 and 300,000 milliseconds per the Infor documentation. API Flows are also bound by the 5-minute global gateway time-out, so a flow of several slow steps can fail even when each step is under its own limit.

What are API Flows in Infor ION?

API Flows are modelled in ION Desk to chain REST API steps, with parallel and decision variants, filters, JQ transforms and Do While loops, and published as one endpoint. They are synchronous end to end and work with JSON only.

Why include a calls-per-minute input?

Many teams throttle their own integrations, and tenants can have usage limits. Total run time is the larger of sequential call time and the throttle-limited time, so a high rate limit does not help when each call is slow, and the reverse.

If you need to move large volumes between an on-premises ERP and Infor OS, or let a private AI assistant call ION APIs safely, we can design the batching and error handling with you.

Talk to an Expert Explore More Free Tools