Infor LN Python API Docs | dltHub
Build a Infor LN-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Infor LN REST API provides access to Infor LN business services and data models through the Infor API Gateway platform. The REST API base URL is {{pu}}{{ot}} (Access Token URL) and the service-specific endpoint provided by Infor API Gateway and all requests require a Bearer token obtained via OAuth 2.0 flow.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Infor LN data in under 10 minutes.
What data can I load from Infor LN?
Here are some of the endpoints you can load from Infor LN:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| items | /items | GET | value | Retrieves a collection of items |
| purchase_orders | /purchase_orders | GET | value | Retrieves a collection of purchase orders |
| sales_orders | /sales_orders | GET | value | Retrieves a collection of sales orders |
| customers | /customers | GET | value | Retrieves a collection of customers |
| inventory | /inventory | GET | value | Retrieves a collection of inventory records |
How do I authenticate with the Infor LN API?
Authentication is handled via Infor API Gateway using OAuth 2.0 (Password Credentials or Client Credentials grant types). Requests require an Authorization header with a Bearer token obtained from the configured access token URL.
1. Get your credentials
To obtain Infor LN REST API credentials, you must register an authorized application within the Infor OS API Gateway: 1. Log in to the Infor OS portal with an account assigned the IONAPI-Administrator role. 2. Navigate to the Navigation Menu, select OS, and go to API Gateway. 3. Navigate to Authorized Apps and click + Add New App. 4. Configure the app settings: specify a Name, select Type as 'Backend Service', and choose a Grant Type (e.g., 'Password Credentials' or 'Client Credentials'). 5. Save the application configuration. 6. Once saved, click the Download Credentials button to export the required configuration as an .ionapi file. This file contains the necessary parameters (Client ID, Client Secret, etc.) for authentication.
2. Add them to .dlt/secrets.toml
[sources.infor_ln_source] client_id, client_secret, username, password = "REPLACE_ME"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Infor LN API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python infor_ln_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline infor_ln_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset infor_ln_data The duckdb destination used duckdb:/infor_ln.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads Authorization and Token from the Infor LN API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def infor_ln_source(client_id_client_secret_username_password=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "{{pu}}{{ot}} (Access Token URL) and the service-specific endpoint provided by Infor API Gateway", "auth": {"type": "bearer", "token": client_id_client_secret_username_password}, }, "resources": [ {"name": "items", "endpoint": {"path": "items", "data_selector": "value"}}, {"name": "purchase_orders", "endpoint": {"path": "purchase_orders", "data_selector": "value"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="infor_ln_pipeline", destination="duckdb", dataset_name="infor_ln_data", ) load_info = pipeline.run(infor_ln_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("infor_ln_pipeline").dataset() sessions_df = data.items.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM infor_ln_data.items LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("infor_ln_pipeline").dataset() data.items.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Infor LN data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Infor LN?
Request dlt skills, commands, AGENT.md files, and AI-native context.