# Infor LN ION API Integration Guide

> Source: https://netray.co/resources/infor-ln-ion-api-integration
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Knowledge Base

## Short answer

Infor ION API guide for LN: when to use the ION API gateway, BOD messaging or file-based exchange, how OAuth 2.0 access works, and how to secure calls.

## Category

infor-ln

## Content

**Intro:** The Infor ION API is the REST interface that the ION API gateway exposes for Infor applications such as LN, protected by OAuth 2.0. Infor ION (Intelligent Open Network) is the integration backbone for Infor LN and the broader Infor ecosystem. ION provides three integration mechanisms: BOD (Business Object Document) messaging for event-driven integration, ION API Gateway for REST API access, and ION Connect for file-based data exchange. Understanding when to use each mechanism and how to configure them is essential for connecting LN to external systems, other Infor products, and cloud services.

**Sections:**

#### ION Architecture and Integration Patterns

**Body:** ION operates as a middleware layer between LN and external systems. BODs are XML-based messages that flow through the ION messaging infrastructure when business events occur in LN, order creation, shipment confirmation, inventory adjustment. The ION API Gateway exposes LN functionality as REST endpoints for real-time request-response integration. ION Connect handles batch file transfers for high-volume data exchange. Choose the pattern based on latency requirements and data volume.

**Bullets:**

- Use BOD messaging for event-driven integration where LN pushes notifications to subscribing systems
- Use ION API Gateway for real-time request-response integration requiring immediate data retrieval or updates
- Use ION Connect for high-volume batch data exchange where real-time processing is not required
- Combine patterns when needed: BODs for events, APIs for data lookup, Connect for bulk synchronization

#### BOD Configuration and Custom BODs

**Body:** LN publishes standard BODs for common business events: SyncItem, ProcessPurchaseOrder, ShipmentReceipt, and dozens more. Each BOD contains a structured XML payload with the business data. Configure BOD publishing in the ION desk by activating the relevant document flows and mapping them to connection points. For events not covered by standard BODs, LN supports custom BOD development through the BOD extension framework.

**Bullets:**

- Activate standard BOD document flows in ION desk for the specific business events your integrations need
- Configure connection points that route BODs from LN to the appropriate receiving systems or queues
- Build custom BODs for LN-specific events not covered by standard Infor BOD definitions
- Implement BOD error handling with dead-letter queues and alerting for failed message processing

#### API Gateway and Security Configuration

**Body:** The ION API Gateway provides secure, authenticated REST API access to LN data and operations. Configure API access by defining API resources in the ION Gateway, mapping them to LN sessions or data objects, and setting up OAuth 2.0 authentication for client applications. Rate limiting, request logging, and access policies protect LN from API abuse while providing the visibility needed for integration troubleshooting.

**Bullets:**

- Configure OAuth 2.0 client credentials for service-to-service integrations through the ION API Gateway
- Define rate limits per API client to prevent integration overload from affecting LN interactive performance
- Enable API request logging for troubleshooting integration issues with complete request and response capture
- Test API integrations in a non-production ION environment before promoting connection configurations to production

**Cta:** Building LN integrations with ION? Our integration architects design scalable, reliable ION architectures.

**Faq:**

#### What is the Infor ION API?

**Answer:** The ION API is the set of REST endpoints published through the ION API gateway in Infor OS. Applications call it with OAuth 2.0 tokens to read and update data in Infor products such as LN. It sits alongside BOD messaging, which handles asynchronous, event-driven document exchange.

#### When should I use the ION API instead of BODs?

**Answer:** Use the ION API for synchronous request and response needs, such as looking up an order or posting a single transaction from another system. Use BODs for event-driven flows where LN publishes changes to subscribers, and batch or file-based exchange for high volume loads.

#### How do I authenticate to the ION API?

**Answer:** Create an API client in the ION API gateway for your service or application, grant it access to the needed APIs, and request OAuth 2.0 tokens with its credentials. Keep separate clients per integration so you can set limits and revoke one without affecting others.

## Related Slugs

- syteline-api-integration-rest
- erp-integration-patterns
- infor-ln-web-ui-customization

## Search terms

ION API, Infor LN ION, ION API integration, LN BOD messaging, Infor ION Gateway, LN integration patterns

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json