Infor ION API Connection Point and Enterprise Connector Setup
infor ion api connection point
Also searched as
- infor ion enterprise connector
- infor ion on premise
- ion connect connection point types
Short answer
A connection point in ION Connect defines how ION talks to one system. An API connection point lets ION call or receive from a REST-style API, while enterprise connectors link ION to ERPs and other applications through Infor-provided integration. Cloud and on-premise deployments differ mainly in networking, security and how connectors are hosted.
Applies to: Infor OS ION Connect, cloud and on-premise. Connection point types and fields vary by version.
How to create an API connection point
- 1In ION Desk open the Connect area and choose to add a new connection point.
- 2Pick the connection point type that matches the endpoint (application, API, database, file or similar types offered in your version).
- 3Give it a clear name and set the base URL, authentication method and credentials or service account.
- 4For inbound calls, define the endpoint and security so the external system can reach ION; for outbound, define headers, content type and timeouts.
- 5Run the built-in connection test and fix certificate, firewall or credential errors before using it in a flow.
- 6Use the connection point as a source or target in a document flow and map the payload.
- 7Monitor the first documents through the ION monitor and check status codes returned by the API.
- 8Store credentials as managed service accounts and rotate them on a schedule.
Connection points and connectors
A connection point is a named endpoint within ION. An enterprise connector is the Infor-supplied integration that sits between ION and a particular application, packaging the protocols and BOD handling for that system.
You configure the application's side and the connection point on the ION side, then describe how documents flow between them.
Cloud versus on-premise
In the cloud, ION is a managed service, so the main concern is reaching your internal systems securely, often through an agent or gateway installed in your network. Outbound-only connectivity is preferred.
On-premise, you run ION on your own grid, which gives control over network placement and data residency but makes you responsible for capacity, patching and certificates. This is attractive where data must not leave the site.
Common setup problems
Authentication failures come first: expired service account keys, wrong tenant or a clock skew on the server. The OAuth failure is covered in the 401 fix page.
Next are TLS trust problems with internal certificate authorities, proxy settings that block outbound calls and payload size or timeout limits on the receiving API.
Try it here, free
SAP RFC Connection Pool Sizing Calculator
Calculate the concurrent RFC connections an external application needs and compare them with gateway and destination limits.
Common pitfalls
- !Using personal credentials for a connection point instead of a service account.
- !Opening inbound firewall holes when an outbound agent would do.
- !Skipping the connection test and discovering certificate issues in production.
- !Not monitoring after go-live, so rejected documents pile up unnoticed.
- !Assuming cloud and on-premise ION have identical features and update timing.
How an ERP-grounded AI assistant handles this
On-prem and air-gapped sites often cannot send integration traces to a cloud tool. A model running locally can read connection definitions and monitor errors, explain failures and suggest fixes while everything stays in the plant network. Netray builds such private assistants around ION and the ERP behind it.
Frequently asked questions
What is an ION connection point?
A configured endpoint in ION Connect that represents a system or interface. Document flows route documents between connection points.
What is an enterprise connector in ION?
An Infor-provided integration component that connects ION to an application such as an ERP, handling that system's protocol and document formats.
Can ION run on premise?
Yes. On-premise Infor OS includes ION, running on your own grid. Features and update cadence can differ from the cloud edition.
Why does my API connection point test fail?
Typical causes are wrong credentials, an untrusted certificate, a blocked proxy or firewall, or a wrong base URL. Check the exact error and the receiving system's logs.
Related
Fix a 401 Unauthorized error from Infor ION API
A 401 from ION API almost always means the credentials in the .ionapi file no longer match what ION API Gateway expects - not that the password is simply wrong. Check whether the Authorized App or service account behind the file was revoked, regenerated, expired, or issued for a different tenant, then re-test with a direct OAuth2 client_credentials call before touching any calling code.
How-toHow to Create an .ionapi File and Service Account in Infor OS
An .ionapi file is a JSON credentials file you download from ION API after registering an Authorized App of type Backend Service and creating a service account for it. It carries the tenant, client id, client secret, the token and authorization endpoints, and the service account keys that your scripts or integrations use to request an OAuth 2.0 access token.
Error fixDiagnose and fix a failed BOD document flow in ION Desk
A Document Flow showing Failed in ION Desk means a BOD (Business Object Document) stopped either at schema validation, at the mapping step, or at the target application. Open the failed instance's detail to see the exact failing element, fix the source data or mapping, then use Resubmit rather than re-triggering the original transaction to avoid duplicates.
How-toHow to query Infor Data Lake with Compass SQL
Compass is the SQL query layer in Infor OS for querying Infor Data Lake, where flattened copies of BODs published over ION are stored by Noun and Verb. Open a Compass SQL Workbench tab, browse the schema for the correct table, and run a filtered SELECT rather than pulling the full history, since Data Lake tables can hold years of append-only data.
Error fixFix a Ming.le homepage widget that will not load
A blank or endlessly spinning Ming.le widget is usually a permissions, session, or backend availability problem, not a broken widget itself. Confirm the issue is widget-specific, check the user's Security Group access to the underlying app, and look at the widget's network calls in browser dev tools to see whether it is failing with 401/403 or simply timing out against a down service.
How-toConnect a Birst Space to Infor Data Lake and build a report
Birst is Infor's embedded BI layer, and the recommended way to report on live Data Lake data is a Live Access source inside a Birst Space rather than a static upload. Build the logical model over a filtered set of tables, apply row-level security, and publish the dashboard to a Ming.le homepage so users reach it without leaving Infor OS.
AI for ERPAI Agents Over Infor ION API, BODs, and the Infor Data Lake
Build AI agents on Infor ION API Gateway, BODs, and Data Lake, alongside or instead of Infor's own GenAI features, with your choice of model and hosting.
AI for ERPOn-Prem AI for CloudSuite Industrial, Without the Multi-Tenant Cloud Move
Add generative AI to CloudSuite Industrial without moving to Infor's multi-tenant cloud. On-prem private LLM options for CSI, with governance and audit built in.
Stuck on Infor ION (Infor OS)?
Talk to engineers who work inside Infor ION (Infor OS) every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
ERP fixes and how-tos
- Infor ION File Template and Email Template: How to Set Them UpHow to set up file connection points in Infor ION, shape file content for a document flow, and set up email notification templates in ION workflows.
- Infor LN integration document types and integration rules with IONHow integration document types and rules work in Infor LN with ION and BODs: what they define, how mapping is set up, and where to debug.
- Diagnose and fix a failed BOD document flow in ION DeskDiagnose a failed BOD document flow in Infor ION Desk: read the error detail, check the mapping, and resubmit safely without duplicating transactions.
Guides
- How to Set Up SyteLine ION IntegrationStep-by-step guide to configuring Infor ION integration with SyteLine CloudSuite Industrial. Learn connection points, BODs, document flows, and ION API gateway setup.
- Infor ION Connect Setup for SyteLine IntegrationConfigure Infor ION Connect for SyteLine data integration. Set up connection points, document flows, BODs, and ION API Gateway for CloudSuite Industrial.
- Infor ION Connect: Integration Configuration GuideConfigure Infor ION Connect integrations. BOD mapping, connection points, workflow automation, and troubleshooting common integration failures.
Integrations
- How to connect Power BI to Infor SyteLineHow to connect Power BI to Infor SyteLine: direct SQL Server, IDO or ION API, data warehouse options, on-prem gateway, key dashboards, and natural-language Q&A.
- How to connect Power BI to Infor LNHow to connect Power BI to Infor LN: direct database, ION and Data Lake options, on-prem data gateway, key manufacturing dashboards and adding natural-language Q&A.