The API Report CardAPI Index
Infor Distribution SX.e

Infor Distribution SX.e API

infor.com

A REST service exists (the SX REST API), but its Swagger reference lives inside customer tenants and community forum threads are the de facto docs. Cloud customers go through the ION API Gateway with OAuth 2.0 and per-tenant .ionapi credentials; nothing is self-serve.

Last verified: July 2026Logistics & Supply Chain
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceFAILNo public reference. The SX REST Service is real, but its Swagger page lives inside each customer tenant.
AccessFAILRequires Authorized App registration in the Infor OS Portal and a .ionapi credential file per tenant.
CoverageGOODThe SX REST Service covers orders, customers, inventory, pricing, and AR/AP, with ION BODs for async document flows.
AuthFAILOAuth 2.0 with 2-hour token TTLs; the refresh and rotation story is poorly documented for server jobs.
Docs & DXFAILThe Swagger reference is in-tenant only; Infor community forum threads are the de facto documentation.
StabilityMIXEDGateway throttling is configurable, but exact limits and 429 backoff semantics surface only in production.
Supergood: Infor Distribution SX.e isn't going to ship an API, so we did: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Infor Distribution SX.e scores F on the API Report Card. A REST service exists (the SX REST API), but its Swagger reference lives inside customer tenants and community forum threads are the de facto docs. Cloud customers go through the ION API Gateway with OAuth 2.0 and per-tenant .ionapi credentials; nothing is self-serve.

Tried to integrate with Infor Distribution SX.e?
SOURCES
The SX REST API Swagger / help page lives inside the customer tenant rather than on a public developer portal, so partners and prospective ISVs cannot evaluate the API surface without an existing customer relationship community.infor.com β†—
Documentation for the SX REST Service API is sparse; community forum threads on the Infor Global Community are the de facto reference for many endpoints community.infor.com β†—
Every external app integrating to CloudSuite Distribution must be registered as an Authorized App in the Infor OS Portal and credentials downloaded as a proprietary .ionapi file, awkward for multi-tenant ISVs onboarding many customer tenants netray.co β†—
OAuth 2.0 access tokens issued by the ION API Gateway default to a 2-hour TTL and the refresh/rotation story is poorly documented for long-lived server-to-server integrations docs.infor.com β†—
The CloudSuite Distribution API surface differs from the on-prem SX.e SX REST Service in subtle ways (auth, base URLs, available endpoints, BOD vs. direct REST patterns), an integrator targeting both deployment models effectively writes two integrations docs.infor.com β†—
The ION API Gateway enforces throttling and rate limits but the exact limits and 429 backoff semantics are not transparently published; partners discover them by hitting them in production aws.amazon.com β†—
BOD XML payloads on the ION bus are large, verbose, and based on the OAGIS standard from the early 2000s; modern JSON-first integrators find the format heavy and the ION mapping tooling dated docs.infor.com β†—
ION Event Hub / webhook-style outbound notifications are configured through ION workflows rather than as self-service webhook subscriptions, increasing setup complexity for downstream consumers developer.infor.com β†—
Calling SX.e / CSD APIs from Postman or curl requires manually parsing the .ionapi file and constructing OAuth headers; community blog posts are the de facto reference rather than first-party documentation linkedin.com β†—
The Progress OpenEdge database layer underneath SX.e is unfamiliar to most modern data engineers and is not directly queryable from standard SQL tools without ODBC drivers and OpenEdge licensing progresstalk.com β†—
Customizations to SX.e screens, IDOs, and ION workflows create version-upgrade fragility, each Infor product update or CSD release requires regression testing of all bespoke API integrations suretysystems.com β†—
Third-party connectors (Conexiom for AP / SOA, Optimizely InsiteConnect, B2B Gateway) are required even for relatively standard integrations because building directly against the SX REST API is too time-consuming for many partners help.conexiom.com β†—
'Does not integrate with CRMs very well', CRM integration (especially to Salesforce and HubSpot) is a chronic pain point spotsaas.com β†—
First-level support is slow and not deeply knowledgeable; bug-fix process is 'very frustrating' and escalations take weeks capterra.com β†—
'EVERYTHING CLOUD', Infor is investing only in CloudSuite Distribution and leaving on-premises SX.e customers behind, including the inability to migrate from the legacy GUI to the modern web UI without a full CSD upgrade g2.com β†—
Reports for combined sales and purchasing data are difficult to produce; standard reporting is dated and customization is costly softwareadvice.com β†—
Customization is tricky and 'very costly when it comes to upgrading', every custom screen, custom field, or custom report has to be re-validated at each upgrade peerspot.com β†—
'Too many screens to get to where you need to work', navigation is dense and the learning curve is steep trustradius.com β†—
Pricing is consistently described as 'more expensive than other comparable ERP solutions on the market' for the distribution segment selecthub.com β†—
Steep learning curve, 'it takes some time getting used to this software, and sometimes it is complex to get used to the functions' subscribed.fyi β†—
Software discontinued / end-of-life concerns, some directories now list SX.e as 'discontinued,' with Infor steering new customers to CloudSuite Distribution only softwareconnect.com β†—
Implementation is multi-month and partner-dependent; named Infor partners (Avaap, NTT DATA Business Solutions, Velocity, Briteskies, RSM) are required for most non-trivial deployments top10erp.org β†—
Progress OpenEdge database layer is unfamiliar to most modern data engineers and is itself a source of integration and reporting friction progresstalk.com β†—