Infor Nexus Datasets
Use this page to set up the Infor Nexus source connector and find reference information.
The Infor Nexus Datasets source connector syncs data from Infor Nexus Data Mesh export datasets. It uses the Infor Nexus Data API (v3.1) with HMAC authentication.
What you’ll need
- An Infor Nexus customer organisation with Data Mesh rights
- An export dataset created in the customer organisation
- A Data API (DAPI) agent user configured in the customer organisation
- These credentials for the DAPI agent user:
- User ID
- Client access key ID
- Secret key
- A Data Key (API Key) for the customer organisation
Set up the connector
Step 1: Configure Infor Nexus
Create a customer organisation
Create a customer organisation in the Infor Nexus platform.
Configure Data Mesh
- Sign in to your Infor Nexus application’s admin console.
- Set up the Data Mesh rule for your organisation.
- Create a user with Data Mesh privileges.
- Confirm that this user can sign in to the Infor Nexus platform.
Create an export dataset
- Sign in to the Infor Nexus platform as the user you created.
- Go to Analytics > Data Mesh Console.
- Click the Export tab to view exportable datasets.
- Click Create to create an export pipeline from the existing models.
- Schedule the dataset to run.
Gather your credentials
Before you configure Airbyte, collect this information:
- Base URL for your Infor Nexus platform
- Dataset name
- DAPI agent user ID
- DAPI agent access key ID
- DAPI agent secret key
- Data key (API key) for your organisation
For more information about HMAC authentication, see Infor Nexus HMAC documentation.
Step 2: Set up the source connector in Airbyte
For Airbyte Cloud:
- Log into your Airbyte Cloud account.
- Click Sources, then click + New source.
- Select Nexus Datasets from the Source type dropdown, then enter a name for this connector.
For Airbyte Open Source:
- Go to the Airbyte Open Source dashboard.
- Click Sources, then click + New source.
- Select Nexus Datasets from the Source type dropdown, then enter a name for this connector.
- Enter the Base URL for your Infor Nexus platform.
- Enter the Dataset Name you want to sync.
- Select the Infor Streaming Mode. Choose
Fullto export the complete dataset, orIncrementalto export changes only. The default isFull.
- Enter the User ID for your DAPI agent user.
- Enter the Access Key ID for your DAPI agent user.
- Enter the Secret Key for your DAPI agent user.
- Enter your organisation’s API Key (Data Key).
- Click Set up source.
Configuration reference
| Field | Type | Required | Description | Default |
|---|---|---|---|---|
base_url | string | Yes | The base URL of your Infor Nexus platform. | |
dataset_name | string | Yes | The name of the dataset to export. | |
mode | string | No | The streaming mode: Full exports the complete dataset; Incremental exports only changes since the last export. | Full |
user_id | string | Yes | The DAPI agent user ID configured in Infor Nexus. | |
access_key_id | string | Yes | The access key ID for the DAPI agent user. | |
secret_key | string | Yes | The secret key for HMAC authentication. | |
api_key | string | Yes | The Data API key for your organization. |
Supported sync modes
The Infor Nexus Datasets source connector supports these sync modes:
- Full Refresh
- Incremental
Supported streams
| Stream Name | Primary Key | Pagination | Supports Full Sync | Supports Incremental |
|---|---|---|---|---|
| datasets | None | Yes | Yes | Yes |
The datasets stream returns records from your configured Infor Nexus export dataset. Each record contains these fields:
raw_data: The record payload as a JSON object.raw_data_string: The record payload as a JSON string.
Limitations and troubleshooting
API response codes
The Infor Nexus Data API returns these status codes during dataset export:
| Status Code | Meaning | Recommended action |
|---|---|---|
| 200 | Dataset is ready to stream. | No action needed. |
| 202 | Dataset is not yet ready. | Wait and retry the sync later. |
| 304 | Dataset is not ready. | Contact Infor member services to investigate. |
IP allow list
If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.
Changelog
Expand to review
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 0.1.16 | 2026-10-09 | 88404 | Mark api_key and secret_key as airbyte_secret |
| 0.1.15 | 2026-10-07 | 88193 | Fix sync failing on every ready export: accept the binary/octet-stream Content-Type the Infor Nexus export returns; treat HTTP 202 (dataset not ready) as a transient error |
| 0.1.14 | 2026-07-28 | 83194 | Update to CDK 7.23.8 (fixes AirbyteCustomCodeNotPermittedError for bundled custom components) and remove the temporary Cloud version override |
| 0.1.13 | 2026-07-28 | 1082 | Roll Cloud back to 0.1.11 — 0.1.12 is built on SDM 7.23.7, which breaks bundled custom components |
| 0.1.12 | 2026-07-28 | 83015 | Update dependencies |
| 0.1.11 | 2026-07-21 | 82494 | Update dependencies |
| 0.1.10 | 2026-07-14 | 81139 | Update dependencies |
| 0.1.9 | 2026-06-23 | 80544 | Update dependencies |
| 0.1.8 | 2026-06-16 | 79933 | Update dependencies |
| 0.1.7 | 2026-06-09 | 78847 | Update dependencies |
| 0.1.6 | 2026-04-28 | 77333 | Update dependencies |
| 0.1.5 | 2026-04-21 | 73832 | Update dependencies |
| 0.1.4 | 2026-04-09 | 76138 | Add missing imports for AirbyteTracedException and FailureType in components.py |
| 0.1.3 | 2026-02-17 | 73548 | Update dependencies |
| 0.1.2 | 2026-02-10 | 73030 | Update dependencies |
| 0.1.1 | 2026-02-03 | 72789 | Add missing registryOverrides to metadata.yaml |
| 0.1.0 | 2025-09-30 | 69349 | Initial release of the Infor Nexus Datasets connector |