The API Report CardAPI Index
THE API REPORT CARD / Enterprise Software / Infor
Infor

Infor API

infor.com

REST APIs across the product lines sit behind the ION API Gateway with OAuth 2.0. The public developer portal has tutorials and an SDK, but real Swagger specs live inside customer tenants, so partners cannot inspect the surface without one. Each CloudSuite speaks a different idiom.

Last verified: July 2026Enterprise Software
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceFAILREST APIs exist behind the ION gateway, but Swagger specs live inside customer tenants, not a public portal.
AccessFAILDiscovery and credentials require an active tenant; partners cannot inspect the real surface without one.
CoverageGOODION API Gateway brokers REST APIs across M3, LN, SyteLine, Lawson, EAM, WMS, and HCM, plus async BODs through ION.
AuthFAILFour parallel OAuth 2.0 grant flows; 2-hour tokens need refresh rotation that integrators miss, causing silent 401s.
Docs & DXGOODdeveloper.infor.com has tutorials and the open-source ION API SDK with Java, .NET, and JavaScript samples.
StabilityMIXEDGateway throttling is tunable per endpoint, but conservative defaults routinely throttle bursty integrations.
MORE FROM THE REPORT CARD
Epicor KineticFAcumaticaD+BrightpearlCEdenC
Supergood: Infor isn't going to ship an API, so we did: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Infor scores F on the API Report Card. REST APIs across the product lines sit behind the ION API Gateway with OAuth 2.0. The public developer portal has tutorials and an SDK, but real Swagger specs live inside customer tenants, so partners cannot inspect the surface without one. Each CloudSuite speaks a different idiom.

Tried to integrate with Infor?
SOURCES
The ION API surface is fragmented across acquired products, M3 uses MI Programs and OData, LN uses OData and BDEs, SyteLine uses IDOs, Lawson uses BODs and DME, integrators must learn a different idiom per CloudSuite suretysystems.com ↗
API discovery is gated, the API Catalog and Swagger definitions live inside a customer's Ming.le tenant rather than a public developer portal; partners cannot inspect the real surface without an active tenant or customer relationship developer.infor.com ↗
Per-endpoint throttling at the ION API Gateway (configurable `spikeArrest.maxRequestsPerPeriod`, `rateSmoothing.delayAfterCount`, etc.) routinely throttles bursty integrations, customers tune throttle policies per integration but defaults are conservative docs.infor.com ↗
OAuth 2.0 access tokens expire every 2 hours and require refresh-token rotation; SDK samples handle this but custom integrators frequently miss it and see silent 401s after long-running jobs docs.infor.com ↗
Four parallel OAuth 2.0 grant flows (Authorization Code, Implicit, Resource Owner, SAML Bearer) with different setup paths inside the ION API admin console, integrators must pick the right one and the docs assume Ming.le familiarity github.com ↗
ION (the integration bus) and the ION API Gateway are distinct concepts often conflated in customer conversations, async BOD publish/subscribe vs synchronous REST gateway require different design patterns docs.infor.com ↗
The downloadable IONAPI credentials file contains client_id, client_secret, identity URL, and token URL, losing/leaking this file effectively grants tenant-wide API access; rotation requires admin action and re-deployment to every integration consumer github.com ↗
Legacy products (Lawson S3, older LN releases, older M3 releases) are exposed through the same ION API Gateway but their underlying APIs (DME queries, BODs, screen-scraped flows) have very different semantics and reliability than the modern REST endpoints community.infor.com ↗
Infor Nexus is on a separate developer portal (developer.infornexus.com) and a separate API stack (AppXpress) from the rest of Infor, partners building cross-platform integrations must manage two completely different developer experiences developer.infornexus.com ↗
API documentation is split across docs.infor.com (product-specific guides, gated to recent product versions), developer.infor.com (gated tutorials/portal, public listing returns 403 for unauthenticated users), and per-customer Ming.le tenants (live Swagger), there is no single canonical reference developer.infor.com ↗
Throttling and service-limit semantics inside Infor OS are not fully documented publicly, customers/partners reference community articles to navigate spike-arrest, concurrent-request, and quota behavior linkedin.com ↗
Event delivery is typically done via ION publishing BODs through the integration bus rather than via a simple HTTP webhook, listeners must implement BOD parsing and reliable delivery semantics rather than plug in a webhook URL docs.infor.com ↗
Sandbox access to evaluate the real ION API surface is effectively only available through Infor customer/partner status, there is no self-service developer-tier tenant comparable to Salesforce/Acumatica/NetSuite sandboxes developer.infor.com ↗
A specialist SI/VAR ecosystem (Surety Systems, RPI Consultants, Lyons Solutions, Briteskies, Avaap) exists explicitly to abstract and operate the Infor API surface, the existence of this consulting market is itself a signal that the surface is too operationally heavy for most customers to self-serve suretysystems.com ↗
Initial implementation and learning the breadth of Infor M3 modules and screens is 'daunting and somewhat cumbersome' for new users, onboarding curve is steep relative to mid-market peers capterra.com ↗
Configuration and deployment is heavily consultant-dependent, customers report that 'a lot of consultants were needed to deploy the application or even to update it' capterra.com ↗
The unified Infor OS / Ming.le UX shell masks a fragmented underlying product portfolio (M3, LN, SyteLine, S3/Lawson, SX.e, FACTS, HMS) acquired over 40+ acquisitions, workflows, terminology, and admin patterns differ by underlying product thecfoclub.com ↗
Advanced modules and workflow customization 'require training and support' and the platform 'can feel overwhelming for new users or smaller teams' thecfoclub.com ↗
Out-of-box reporting depth varies widely by CloudSuite, and Birst overlay is frequently purchased separately to fill analytics gaps softwareadvice.com ↗
Long-tenured customers on older releases (LN 10.x, M3 13.x, SyteLine 10.x, Lawson 9/10) face multi-year, multi-million-dollar re-implementation paths to reach a current CloudSuite multi-tenant SKU suretysystems.com ↗
Customer support escalation paths and case resolution times are inconsistent across product lines, Trustpilot reviewers cite slow turnaround on hard tickets trustpilot.com ↗
Pricing is not transparent, list pricing for CloudSuite SKUs is not published, and CFOs depend on Infor sales or VAR partners to scope user-count, module, and resource-tier multipliers erp-pilot.com ↗
Total cost of ownership for an enterprise CloudSuite deployment is significant, implementation alone is commonly $200K–$1M+ at 100 users with 3-year TCO of $900K–$2.4M erp-pilot.com ↗
Switching off Infor (especially Lawson S3 in healthcare or Lawson HCM in public sector) is treated as a generational re-platform; customer churn risk to Workday and Oracle Fusion is a public competitive theme workday.com ↗
© Supergood Systems, Inc.