.png)
Infor Nexus Integration Guide
Connect Infor Nexus supply-chain data with enterprise applications through REST APIs, selected callbacks, scheduled workflows, and document interfaces.
Infor Nexus integration options at a glance
Infor Nexus is primarily integrated through tenant-specific REST APIs for accessing and exchanging Purchase Orders, Shipments, Invoices, Items, Trading Partners, and related supply-chain data. Selected tenants or processes may provide outbound callbacks or event notifications, while bulk, asynchronous, import-oriented, and document interfaces depend on the enabled resource and module. OAuth 2.0 and application permissions are commonly used, but the exact flow must be confirmed with the tenant administrator. Martini can consume authenticated APIs, receive supported callbacks, schedule incremental synchronization, transform JSON, XML, CSV, and spreadsheet data, and orchestrate document transfers where the relevant endpoint is available.
| Integration point | Supported by Infor Nexus? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | The principal integration method for querying and updating Purchase Orders, Shipments, Invoices, Items, Trading Partners, statuses, and business documents. Exact resources and API versions are tenant-specific. | Martini can consume authenticated REST APIs from workflows, map request and response payloads, expose controlled APIs for upstream systems, and handle pagination, checkpoints, and errors. |
| Webhooks / outbound callbacks | Limited | Selected Infor Nexus processes or events may provide outbound callbacks or event notifications. Coverage should not be assumed for every object, status, or tenant. | Martini can expose a webhook-facing API or use a workflow start trigger to receive supported notifications, validate the source, retrieve current data, and process at-least-once delivery safely. |
| Bulk / async / batch APIs | Limited | Bulk, asynchronous, or import-oriented processing may be available for selected resources and high-volume processes such as shipment updates, Purchase Order lines, or Invoices. | Martini can implement controlled batching, asynchronous orchestration, pagination, retry handling, checkpointing, and reconciliation when the tenant exposes the required mechanism. |
| File / attachment APIs | Limited | Infor Nexus supports supply-chain and commercial document exchange, but upload, download, attachment, format, and size capabilities vary by module, document type, and API resource. | Martini can transform JSON, XML, CSV, and spreadsheet content and orchestrate document transfer through the relevant Infor Nexus API or file endpoint. |
| Authentication | Yes | API access requires configured authentication and authorization. OAuth 2.0 with application credentials is commonly used, while exact grants, scopes, roles, and endpoints depend on the tenant and Infor security model. | Martini can store secrets and environment-specific configuration securely, acquire or refresh tokens where required, and send authenticated requests from workflows or exposed APIs. |
| Scheduled synchronization | Yes | Polling supports incremental synchronization, reconciliation, historical loads, and objects for which event delivery is unavailable or not enabled. | Martini can start workflows on a schedule, use modified timestamps or status filters, persist checkpoints, apply replay windows, and resume after partial failures. |
| Database access | Not confirmed | Direct customer database or analytics access is not confirmed and should not be assumed for Infor Nexus integrations. | Martini should use documented APIs, approved exports, files, callbacks, or Infor integration services rather than direct database connectivity. |
How Infor Nexus exposes data and business events
Infor Nexus REST APIs
Infor Nexus is primarily integrated through tenant-specific REST APIs. These APIs support querying and updating supply-chain objects, submitting transactions, retrieving statuses, and exchanging business documents, subject to the resources and versions enabled for the tenant.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates with the tenant-approved method, calls the required resource, maps the response into a canonical model, applies business rules, and writes the result to an enterprise target or exposes a controlled downstream API.
Implementation sequence
Infor Nexus callbacks and event notifications
Infor Nexus may provide outbound callbacks, event subscriptions, or notification endpoints for selected processes and events. Coverage is not universal and must be confirmed for the tenant, object, and status being integrated.
Martini implementation pattern
Martini implementation pattern: expose an authenticated webhook-facing API or workflow trigger, validate the notification, retrieve the current Infor Nexus resource when necessary, and use an event identifier or stable object key to make processing idempotent.
Implementation sequence
Infor Nexus bulk and asynchronous processing
Bulk, asynchronous, or import-oriented mechanisms may be available for selected high-volume resources and processes. Availability, status handling, and completion semantics must be confirmed for the specific API resource.
Martini implementation pattern
Martini implementation pattern: partition source data into controlled batches, submit supported requests, monitor asynchronous results where available, and reconcile accepted, rejected, and incomplete items without rerunning successful work.
Implementation sequence
Infor Nexus documents and attachments
Infor Nexus supports supply-chain and commercial document exchange, but document upload, download, attachment, format, and size behavior depends on the enabled module and API resource.
Martini implementation pattern
Martini implementation pattern: retrieve document metadata or content through the confirmed interface, stage or transform the file when needed, preserve its relationship to the Purchase Order, Shipment, Invoice, or partner, and transfer it to the target application.
Implementation sequence
Infor Nexus authentication
Infor Nexus API access requires tenant-specific authentication and authorization. OAuth 2.0 application credentials are commonly used, but the grant, token URL, scopes, roles, and broader Infor OS or ION security model must be confirmed.
Martini implementation pattern
Martini implementation pattern: store client credentials and endpoint configuration as secured environment values, obtain or refresh an access token in the workflow, send only authorized requests, and route authentication failures separately from retryable service errors.
Implementation sequence
Common Infor Nexus integration patterns
Pattern 1: Synchronize Purchase Orders with an ERP
When to use this pattern
Use this pattern when an ERP is the system of record for approved purchasing and Infor Nexus is used for buyer, supplier, and trading-partner collaboration. The workflow can also retrieve acknowledgements, exceptions, or changes for the ERP.
Integration direction
Example Mapping
| Infor Nexus Field | Canonical Field | Target Field |
|---|---|---|
| PurchaseOrderNumber | purchaseOrder.externalId | PurchaseOrder.PurchaseOrderNumber |
| Supplier | tradingPartner.supplierId | Supplier.ExternalId |
| OrderLines | purchaseOrder.lines | PurchaseOrderLine.Items |
| RequestedDeliveryDate | line.requestedDeliveryDate | Schedule.RequiredDate |
Martini implementation pattern
Martini receives an approved ERP transaction through an API or scheduled retrieval, validates required supplier, item, line, and delivery data, maps it to the Infor Nexus Purchase Order model, and submits it through the REST API. Stable order references prevent duplicate creation; validation failures are routed for correction, while transient API failures use bounded retries and reconciliation.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- error handling
- scheduled synchronization
Pattern 2: Synchronize Shipments and Milestones
When to use this pattern
Use this pattern to provide ERP, transportation, customer-facing, or operational applications with current Shipment and Shipment Milestone information. Supported callbacks can reduce latency, while polling provides coverage for unsupported events and reconciliation.
Integration direction
Example Mapping
| Infor Nexus Field | Canonical Field | Target Field |
|---|---|---|
| ShipmentReference | shipment.externalId | Shipment.Reference |
| Carrier | shipment.carrier | Shipment.Carrier |
| MilestoneType | shipmentMilestone.type | Shipment.Status |
| ActualEventDate | shipmentMilestone.occurredAt | Shipment.LastEventAt |
Martini implementation pattern
Martini receives a supported notification or runs an incremental workflow using modified timestamps or status filters. It retrieves the current resource, maps carrier and milestone data, applies event-ordering and deduplication rules, and updates Salesforce or another target. Checkpoints, replay windows, and retry queues protect against missed events and temporary failures.
Martini capabilities used
- webhook-facing APIs
- workflow triggers
- scheduled workflows
- data mapping
- idempotency rules
- retry handling
Pattern 3: Process Invoices and Commercial Documents
When to use this pattern
Use this pattern when Infor Nexus contains Invoices and related commercial documents that must be validated and delivered to an accounts-payable or ERP platform. The reverse direction can publish payment or exception status where the applicable API supports it.
Integration direction
Example Mapping
| Infor Nexus Field | Canonical Field | Target Field |
|---|---|---|
| InvoiceNumber | invoice.externalId | Invoice.InvoiceNumber |
| PurchaseOrderReference | invoice.purchaseOrderId | Invoice.PurchaseOrder |
| InvoiceTotal | invoice.totalAmount | Invoice.Total |
| DocumentReference | document.sourceReference | InvoiceAttachment.Reference |
Martini implementation pattern
A Martini workflow retrieves Invoices and associated document metadata, validates references, totals, currencies, and required Trading Partner relationships, then maps and writes the result to the ERP. Documents are staged or transferred through the confirmed interface, while business-rule failures are quarantined and transient API or file failures are retried without creating duplicate invoices.
Martini capabilities used
- API consumption
- file handling
- JSON and XML transformation
- validation
- business rules
- error handling
Pattern 4: Synchronize Trading Partners and Items
When to use this pattern
Use this pattern for master-data alignment between Infor Nexus and an ERP or procurement platform. It is useful when suppliers, factories, Items, or Products must be created or updated consistently before dependent Purchase Orders or Shipments are processed.
Integration direction
Example Mapping
| Infor Nexus Field | Canonical Field | Target Field |
|---|---|---|
| TradingPartnerId | partner.externalId | Vendor.ExternalId |
| PartnerName | partner.name | Vendor.Name |
| ItemNumber | item.externalId | Item.SKU |
| PackagingQuantity | item.packagingQuantity | Item.PackagingQuantity |
Martini implementation pattern
Martini retrieves changed Trading Partners and Items, normalizes identifiers and units, applies required-field and deduplication rules, and updates NetSuite or another target. The workflow preserves tenant and object scope, processes master data before dependent transactions, and records rejected items for correction and later reconciliation.
Martini capabilities used
- scheduled synchronization
- API consumption
- data mapping
- validation
- deduplication
- workflow orchestration
Applications commonly integrated with Infor Nexus
Infor Nexus can be connected with ERP, procurement, customer-facing, service-management, and transportation applications to coordinate supply-chain transactions and visibility. The following are practical enterprise integration targets; specific packaged integrations and resource availability should be confirmed with the relevant application and Infor Nexus tenant.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Exchange Purchase Orders, supplier confirmations, shipment information, invoices, and material data between the ERP and the supply-chain network. | SAP S/4HANA → Martini → Infor Nexus | Martini exposes or consumes APIs for approved ERP events, validates and maps SAP business objects to Infor Nexus payloads, and uses REST workflows for submission, status retrieval, retries, and reconciliation. |
| Oracle Fusion Cloud ERP | Synchronize procurement, receiving, invoices, suppliers, and payment-related status with supply-chain collaboration processes. | Oracle Fusion Cloud ERP → Martini → Infor Nexus | A Martini workflow retrieves or receives ERP changes, maps supplier and transaction identifiers, submits supported Infor Nexus requests, and routes validation or transient failures for retry and review. |
| Microsoft Dynamics 365 | Connect purchasing, inventory, fulfillment, supplier, and financial processes with Infor Nexus collaboration data. | Microsoft Dynamics 365 → Martini → Infor Nexus | Martini orchestrates bidirectional API workflows, applies business rules to order and shipment data, preserves external identifiers, and performs scheduled reconciliation for missed or changed objects. |
| Salesforce | Provide customer-facing teams with order, shipment, and delivery visibility, or send customer and order context into downstream supply-chain processes. | Infor Nexus → Martini → Salesforce | Martini retrieves shipment and milestone data from Infor Nexus, normalizes it for Salesforce objects, and applies filtering and deduplication before updating customer-facing records. |
| ServiceNow | Create incidents or operational tasks for shipment exceptions, supplier issues, customs delays, or integration failures. | Infor Nexus → Martini → ServiceNow | A callback or scheduled Martini workflow detects selected exceptions, enriches them with shipment and partner context, and creates or updates ServiceNow incidents with idempotent correlation fields. |
| Coupa | Align procurement and supplier information, Purchase Orders, Invoices, and supplier collaboration data. | Coupa → Martini → Infor Nexus | Martini maps approved procurement transactions and supplier identifiers, submits supported Infor Nexus requests, and sends invoice or fulfillment status back to Coupa where the target APIs permit it. |
| NetSuite | Synchronize purchasing, inventory, suppliers, shipments, and invoices for organizations using NetSuite as a financial or ERP platform. | NetSuite → Martini → Infor Nexus | Scheduled or event-started workflows retrieve changes from both systems, transform object relationships, enforce stable external references, and reconcile incomplete or rejected transactions. |
| Project44 | Combine transportation visibility events with Infor Nexus Shipment and Shipment Milestone data. | Project44 → Martini → Infor Nexus | Martini receives or polls transportation events, correlates them with Infor Nexus shipment references, applies event-ordering rules, and publishes supported updates or consolidated visibility data. |
How to build a Infor Nexus integration in Martini
Objective
Establish the tenant-specific Infor Nexus connection and confirm the permitted API resources, scopes, roles, endpoints, and environment settings.
Instructions in Martini
- Confirm the tenant authentication flow, token endpoint, scopes, and API base URL
- Store client credentials, tenant identifiers, and endpoint configuration in Martini secrets or environment configuration
- Test access against a non-production tenant where available
Objective
Select an event-driven, scheduled, or API-led start based on the Infor Nexus resource and the required synchronization latency.
Instructions in Martini
- Use a supported callback or event notification for selected processes
- Use a scheduler for polling, reconciliation, historical loads, or unsupported event coverage
- Expose a Martini API when an upstream application needs to initiate the process
Objective
Obtain the current Infor Nexus object or document and account for pagination, continuation state, and related-object dependencies.
Instructions in Martini
- Call the required REST resource or process the incoming notification
- Retrieve the current resource when a callback contains only a reference
- Persist pagination state and use modified-time filters or checkpoints for incremental synchronization
Objective
Coordinate API calls, parent-child relationships, enrichment, batching, and asynchronous processing in a maintainable Martini workflow.
Instructions in Martini
- Process required parent objects before dependent objects
- Use controlled concurrency for high-volume Shipment, Invoice, or Purchase Order processing
- Track correlation identifiers and separate synchronous from asynchronous outcomes
Objective
Convert Infor Nexus payloads and documents into the canonical model required by the target application while preserving business relationships.
Instructions in Martini
- Map actual Infor Nexus object fields to target fields
- Transform JSON, XML, CSV, spreadsheet, or document content as required
- Preserve stable identifiers for Purchase Orders, Shipments, Invoices, Items, Trading Partners, and Documents
Objective
Validate required fields, enforce business conditions, and prevent duplicate creates before writing to the target system.
Instructions in Martini
- Validate references, totals, dates, statuses, and required partner relationships
- Use object identifiers, event identifiers, or external references as idempotency keys
- Route business validation failures separately from authentication, rate-limit, and transient service errors
Common Infor Nexus data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Purchase Orders | Buyer instructions and order-line commitments shared with suppliers and other trading partners. | SAP S/4HANA, Oracle Fusion Cloud ERP, Microsoft Dynamics 365, Coupa, NetSuite | Martini validates order references and lines, maps delivery requirements and partner identifiers, submits or retrieves REST representations, and uses stable external references for idempotent updates. |
| Shipments | Transportation and shipment records containing references, dates, quantities, and status information. | ERP platforms, Project44, Salesforce, data warehouses, customer-facing applications | Martini retrieves or receives shipment changes, correlates them with Purchase Orders and Trading Partners, transforms milestone and quantity data, and checkpoints incremental processing. |
| Shipment Milestones / Events | Logistics status changes such as booking, departure, arrival, and delivery. | Salesforce, ServiceNow, Project44, ERP platforms, operational data stores | Martini processes supported callbacks or polls for changes, orders or deduplicates events, enriches them with shipment context, and routes exceptions for retry or reconciliation. |
| Invoices | Commercial invoices associated with Purchase Orders, Shipments, suppliers, and buyers. | SAP S/4HANA, Oracle Fusion Cloud ERP, Microsoft Dynamics 365, Coupa, NetSuite | Martini validates required references and totals, maps invoice data and related documents, submits or retrieves API payloads, and separates business validation failures from transient transport errors. |
| Items / Products | Item, SKU, packaging, quantity, and product master information used in supply-chain transactions. | SAP S/4HANA, Oracle Fusion Cloud ERP, Microsoft Dynamics 365, NetSuite, master-data stores | Martini normalizes identifiers and units, applies validation and deduplication rules, and synchronizes creates or updates using tenant-appropriate API resources. |
| Trading Partners | Suppliers, buyers, carriers, factories, banks, and other participants in the supply-chain network. | ERP platforms, Coupa, NetSuite, ServiceNow, master-data platforms | Martini maps partner roles and identifiers, validates required attributes, preserves tenant or partner scope, and prevents duplicate creation through external keys. |
Authentication and security considerations
Tenant-specific authentication
Infor Nexus authentication depends on the tenant, API product, and whether access is provisioned directly through Infor Nexus or through the broader Infor security model. OAuth 2.0 application credentials are commonly used, but the grant, token URL, scopes, and roles must be confirmed.
Secure configuration
- Store client secrets, tokens, tenant identifiers, API URLs, and environment values in Martini secrets or secured configuration.
- Use application identities for scheduled and backend workflows rather than interactive user credentials.
- Use HTTPS for API traffic and callback endpoints.
- Validate callback authentication, source information, signatures, replay controls, and any IP restrictions before processing notifications.
Operational considerations for Infor Nexus integrations
Reliable synchronization
Confirm tenant-specific rate limits, concurrency behavior, pagination, continuation tokens, and API versioning before production deployment. Use controlled concurrency, bounded exponential backoff for transient 429 and 5xx responses, durable checkpoints, and replay windows for late-arriving changes.
Data integrity
- Use stable object and event identifiers to make retries idempotent.
- Preserve relationships among Purchase Orders, Shipments, Invoices, Items, Trading Partners, and Documents.
- Separate validation, authorization, rate-limit, transient service, and business-rule failures.
- Confirm document size, MIME type, retention, and attachment behavior before transferring large files.
- Test mappings against a non-production tenant and monitor schema, resource, and API version changes.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration beyond point-to-point scripts
Martini provides a maintainable workflow layer around Infor Nexus APIs, callbacks, schedules, and document interfaces. It can centralize authentication, pagination, checkpoints, transformations, business rules, retries, and reconciliation instead of duplicating them across application-specific scripts.
Reusable integration assets
- Expose controlled APIs that hide tenant-specific Infor Nexus details from upstream applications.
- Reuse mappings, validation logic, and error-handling patterns across Purchase Orders, Shipments, Invoices, and master data.
- Combine event-driven processing with scheduled polling when callback coverage is limited.
- Monitor workflow execution and route failed records for correction and replay.
Frequently asked questions
Infor Nexus is primarily integrated through tenant-specific REST APIs for Purchase Orders, Shipments, Shipment Milestones, Invoices, Items, Trading Partners, and related documents. Selected tenants or processes may also provide outbound callbacks or event notifications, while scheduled polling supports incremental synchronization and reconciliation. File and document interfaces depend on the enabled module and API resource.
Yes. Martini can consume authenticated Infor Nexus REST APIs, receive supported callbacks or event notifications, run scheduled synchronization workflows, transform supply-chain data, and expose APIs for upstream or downstream applications. The exact resources and event coverage depend on the Infor Nexus tenant configuration.
No dedicated Infor Nexus connector is required. Martini can integrate using Infor Nexus REST APIs, supported callbacks, scheduled workflows, document or file interfaces, and the tenant-approved authentication methods. A native Martini connector was not confirmed in the supplied information.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Infor Nexus. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Infor, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.
Use the Infor Nexus REST APIs as the primary method and confirm the exact resource and version for the tenant. Use callbacks or event notifications when the required process supports them, and use scheduled incremental synchronization for unsupported events, historical loads, and reconciliation. Bulk, asynchronous, and document interfaces should be adopted only after resource-specific confirmation.
Infor Nexus may provide outbound callbacks, event subscriptions, or notification endpoints for selected processes and events, but coverage is not universal across objects or statuses. Martini can receive supported notifications through an authenticated API or workflow trigger and can fall back to polling where event delivery is unavailable.
Martini can use modified timestamps, status filters, event identifiers, pagination state, and durable checkpoints for incremental synchronization. Stable Infor Nexus object IDs, purchase-order numbers, shipment references, invoice numbers, and external references can serve as idempotency keys so retries update existing target objects instead of creating duplicates.
Yes. Martini can expose a controlled API for upstream applications, validate and transform requests, orchestrate calls to Infor Nexus, and return a governed response. This can isolate tenant-specific authentication, resource mappings, business rules, retries, and error handling from consuming applications.
Related Martini documentation
Workflows
Connect Infor Nexus with your enterprise systems
Use Martini to build secure, maintainable Infor Nexus integrations across supply-chain data, events, documents, and enterprise applications.