# Infor M3 SDK, MI APIs and REST API Documentation Guide

> Source: https://netray.co/erp-help/infor-m3-sdk-mi-api-rest-documentation-guide
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

There is no single M3 SDK. Developers use a set of tools: MI programs (the API layer over Business Engine), the REST endpoint that exposes them, the H5 client SDK for scripts and extensions, and the Grid and ION tooling around them. Start with MI programs and REST, and use the official Infor documentation for the transaction list.

## Kind

advanced

## System

infor-m3

## Erp

Infor M3

## Module

M3 SDK / MI APIs / REST

## Query

infor m3 sdk

## Alternate Queries

- sdk infor m3
- infor m3 rest api documentation
- m3 mi programs list
- m3 api developer guide

## Applies To

Infor M3 Business Engine, on-prem and CloudSuite. Endpoint paths and authentication differ between on-prem and cloud.

## Steps

### Make your first M3 API call

**Items:**

- Find the MI program for the business object, for example one for items, one for customers. The names end in MI, such as a program per master data area.
- Open the transaction list for that program in the API documentation or the M3 API metadata programs, and read input and output fields and which are mandatory.
- Get credentials. In the cloud, create an ION API authorized app and a service account and download the credential file. On-prem, check how your Grid is secured.
- Request an access token with OAuth 2.0 where ION API is used, and send it as a bearer token.
- Call the execute endpoint with program, transaction and parameters, as a GET for reads.
- Parse the JSON, which returns the records in a list and an error block with the message when a transaction fails.
- Handle paging and limits for list transactions, and log the full error text.

## Sections

### The pieces of the developer surface

**Body:**

MI programs are the supported API. Each program has transactions, with named input and output fields, that wrap Business Engine logic so that validation rules still run. They are the right way to read and write M3 data from outside.

The REST interface exposes MI transactions over HTTP with JSON. The H5 client has its own scripting SDK for personalization and extensions in the UI. Event Analytics, Grid applications and MEC for EDI are separate tools around the core.

### Example REST call shape

**Body:**

The URL shape below is the commonly documented pattern. Your base host, tenant segment and version prefix depend on your deployment, so copy the base URL from your ION API or Grid configuration.

Read calls are GET requests with the field values as query parameters. Write calls use the same pattern with the add, change or delete transaction names.

**Code:**

- GET https://<host>/<tenant>/M3/m3api-rest/v2/execute/MMS200MI/GetItmBasic?ITNO=ITEM-123
- Authorization: Bearer <access token>
- Accept: application/json

### Rules that save time

**Body:**

- Use a dedicated service user whose roles allow only the programs needed. An unauthorized program returns a not-authorized error rather than data.
- Send dates as YYYYMMDD and numbers without locale separators. For list transactions set a maximum returned records value and page through the result.
- Prefer MI transactions to direct SQL for writes. For reads at scale, use a reporting replica or the data lake rather than hammering the API.

## Pitfalls

- Writing to M3 tables with SQL instead of MI transactions.
- Using a personal account for integrations, so the role or password change breaks the flow.
- Ignoring the error block and treating HTTP 200 as success.
- Missing mandatory fields because the documentation was for another version.
- Not paging list transactions and silently truncating results.

## Ai Angle

Agents that act on M3 should call MI transactions under a narrow service role and ask for human approval on writes. Netray builds such tool layers, typically with an open-weight model served on your own GPUs, so prompts and records stay inside your network.

## Faq

### Is there a download called the M3 SDK?

**Answer:** Infor ships several development components rather than one package. Which you need depends on whether you are calling APIs, extending the H5 UI or building Grid applications. Check the Infor documentation library for your version.

### Where is the REST API documentation?

**Answer:** In the Infor documentation library and the ION API section of your tenant, plus the API metadata inside M3 for the transaction list and fields of each MI program.

### Can I call M3 APIs without ION API?

**Answer:** On-prem installations can expose the endpoints through Grid with their own authentication. In the cloud, ION API is the supported route.

## Search terms

infor m3 sdk, sdk infor m3, infor m3 rest api documentation, m3 mi programs, m3 api execute endpoint, m3 ion api oauth, m3 h5 sdk, infor m3 developer guide

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