Infor · Schema

Infor M3 Customer

JSON Schema for an Infor M3 (CloudSuite Industrial) customer record as returned by CRS610MI/GetBasicData and related transactions. Maps to CRS Customer file.

ERPManufacturingSupply ChainCloudIntegration

Properties

Name	Type	Description
CUNO	string	Customer number
CUNM	string	Customer name
CUA1	string	Address line 1
CUA2	string	Address line 2
CUA3	string	Address line 3 / city
CUA4	string	Address line 4
PONO	string	Postal code
PHNO	string	Telephone number 1
PHN2	string	Telephone number 2
EMAL	string	Email address
CSCD	string	Country code (ISO 3166-1 alpha-2 or alpha-3)
WHLO	string	Warehouse (default delivery warehouse)
LNCD	string	Language code
CUCD	string	Currency code (ISO 4217)
STAT	string	Customer status (10=Active, 20=Inactive, 90=Closed)
STDT	string	Status date (YYYYMMDD format)
CUTP	integer	Customer type (0=Standard, 1=Miscellaneous)
ALCU	string	Search key (alias for customer number)
TEPY	string	Payment terms code
TEDL	string	Delivery terms code
MODL	string	Delivery method code
CRTP	integer	Exchange rate type

View JSON Schema on GitHub

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://api-evangelist.github.io/infor/json-schema/infor-m3-customer-schema.json",
  "title": "Infor M3 Customer",
  "description": "JSON Schema for an Infor M3 (CloudSuite Industrial) customer record as returned by CRS610MI/GetBasicData and related transactions. Maps to CRS Customer file.",
  "type": "object",
  "properties": {
    "CUNO": {
      "type": "string",
      "maxLength": 10,
      "description": "Customer number"
    },
    "CUNM": {
      "type": "string",
      "maxLength": 36,
      "description": "Customer name"
    },
    "CUA1": {
      "type": "string",
      "maxLength": 36,
      "description": "Address line 1"
    },
    "CUA2": {
      "type": "string",
      "maxLength": 36,
      "description": "Address line 2"
    },
    "CUA3": {
      "type": "string",
      "maxLength": 36,
      "description": "Address line 3 / city"
    },
    "CUA4": {
      "type": "string",
      "maxLength": 36,
      "description": "Address line 4"
    },
    "PONO": {
      "type": "string",
      "maxLength": 10,
      "description": "Postal code"
    },
    "PHNO": {
      "type": "string",
      "maxLength": 16,
      "description": "Telephone number 1"
    },
    "PHN2": {
      "type": "string",
      "maxLength": 16,
      "description": "Telephone number 2"
    },
    "EMAL": {
      "type": "string",
      "maxLength": 80,
      "format": "email",
      "description": "Email address"
    },
    "CSCD": {
      "type": "string",
      "maxLength": 3,
      "description": "Country code (ISO 3166-1 alpha-2 or alpha-3)"
    },
    "WHLO": {
      "type": "string",
      "maxLength": 3,
      "description": "Warehouse (default delivery warehouse)"
    },
    "LNCD": {
      "type": "string",
      "maxLength": 2,
      "description": "Language code"
    },
    "CUCD": {
      "type": "string",
      "maxLength": 3,
      "description": "Currency code (ISO 4217)"
    },
    "STAT": {
      "type": "string",
      "enum": ["10", "20", "90"],
      "description": "Customer status (10=Active, 20=Inactive, 90=Closed)"
    },
    "STDT": {
      "type": "string",
      "description": "Status date (YYYYMMDD format)"
    },
    "CUTP": {
      "type": "integer",
      "description": "Customer type (0=Standard, 1=Miscellaneous)"
    },
    "ALCU": {
      "type": "string",
      "maxLength": 10,
      "description": "Search key (alias for customer number)"
    },
    "TEPY": {
      "type": "string",
      "maxLength": 3,
      "description": "Payment terms code"
    },
    "TEDL": {
      "type": "string",
      "maxLength": 3,
      "description": "Delivery terms code"
    },
    "MODL": {
      "type": "string",
      "maxLength": 3,
      "description": "Delivery method code"
    },
    "CRTP": {
      "type": "integer",
      "description": "Exchange rate type"
    }
  },
  "required": ["CUNO", "CUNM"]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this

find_json_schemasBrowse and filter every JSON Schema in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This JSON Schema

curl "https://apis.io/api/v1/json-schemas/infor-m3-customer"

All schemas

curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.