FLRT JSON API Docs

Dive into DevOps by automating your Power Systems reports using our JSON APIs. This page will be updated as we provide more APIs in the future.
If you find any bugs or errors, please report them through our Feedback Tool.

API Reference

• Power Systems Recommendations
• FLRT Lite
• Power Devices Adapter Microcode

The API used to access FLRT data is a REST style interface implemented using the HTTPS protocol. This enables faster development because API queries can be tested using a browser. You can begin to get familiar with this API interface by building a query URL using FLRTs Report Input page on the Web:
https://esupport.ibm.com/customercare/flrt/power

The FLRT Report input page provides a form to specify your system. This is the preferred method if you have one or two systems. The HTTP request built by the FLRT input page is almost identical to that needed by the API.

To access FLRT programmatically you could use the curl command or you can use the axios package in NodeJS or Python's request library.
The Power software that FLRT has data for is listed on this page: Products and Codes

If you have many systems, you may want to automate the query through scripting. This section will describe how to manually construct a URL to query FLRT Recommendations.

Example query to get a JSON-formatted report using an HTTP GET request:
https://esupport.ibm.com/customercare/flrt/report?format=json&plat=power&p0.mtm=9119-MHE&p0.fw=SC860_160&p0.hmc=V9+R1+M921&p0.hmchost=7042-CR9&p1.parnm=Partition+1&p1.os=ibmi&p1.ibmi=V7R3M4&p2.parnm=Partition+2&p2.os=aix&p2.aix=7200-03-01

GET https://esupport.ibm.com/customercare/flrt/report

GET https://esupport.ibm.com/customercare/flrt/query

Format Type

Partitions must be prefixed with p#, where # must start from 1 and can go up to 999 partitions. The limitation is mainly based on the maximum URL length of 2048 characters. Partitions 1000 and 1001 have special meaning and should not be used here.
For example: p1.os=aix&p1.aix=7100-01-01

Software products are attached to a partition, as they will be linked to a specific operating system.

The JSON response returns an object with the "flrtReport" key that holds an array of objects, where System is first that contains MTM, FW, HMC, and the Partitions with OS information follow.

High level structure of JSON response

flrtReport (array of partition)

	System (partition object)
		fw (product object)
		hmc (product object)
		hmchost (product object)
		kvm (product object)
		fsm (product object)
		mtm (product object)
	
	Partition 1 (partition object)
		[OS Name] (product object)

Each product object under System or Partitions will have the following structure:

fw (product object)
	name (string)
	nickname (string)
	key (string)
	code (string)
	input (version object)
	update (version object) - only if exists
	upgrade (version object) - only if exists
	minimum (version object) - only if exists

Each version object is used for input, update, upgrade, and minimum and will have the following structure:

input (version object)
	name (string)
	version (string)
	releaseDate (string date)
	eosps (string date) - if available
	url (string url) - if available
	download (string url) - if available
	fixDetails (string url) - if available
	reboot (Boolean) - aix only
	notes (array) - array of objects with key of note or fix
	latest (array) - version object
	apars (object) - aix only

Notes array will have the following structures

notes (array of notes/fixes)
	(notes object)
		note (string)
	(fixes object)
		fix (object)
			version (string)
			description (string)
			url (string url)
			download (string url)
			rerleaseDate (string date)

APAR objects which appear for partitions with AIX, have the following structure:

apars (object)
	OTHER (object)
		[CVE | APAR] (apar object)
			url (string url)
			bulletin (string url)
			download (string url)
			filesets (string)
			fixedIn (string)
			fixedInLink (string)
			abstract (string)
			ifixes (string)
			issued (string date)
			updated (string date)
			reboot (string bool)
	HIPER (object)
		(apar objects)
	SECURITY (object)
		(apar objects)

FLRT Lite is our raw list of version data. There is no dependency logic in FLRT Lite, but it may be used to validate your version strings when using them as input in our queries.

FLRT Lite website:
https://esupport.ibm.com/customercare/flrt/liteHome

Here is an example for Hardware Management Consoles (HMC):
https://esupport.ibm.com/customercare/flrt/liteTable?prodKey=hmc

JSON format is retrieved by adding the format=json URL parameter:
https://esupport.ibm.com/customercare/flrt/liteTable?prodKey=hmc&format=json

GET https://esupport.ibm.com/customercare/flrt/

JSON response structure has the following:

results (array of version)
	(version object)
		input (string)
		inputurl (string url)
		update (string)
		updateurl (string)
		ga (string date)
		eosps (string date)

JSON Response example:
https://esupport.ibm.com/customercare/iprt/prq-table?mtm=8231-E2B&fc=0047%2C0265%2C0839&os=&format=json

GET https://esupport.ibm.com/customercare/iprt/prq-table

prqSet (array of prereq)
	(prereq object)
		machineType (string)
		model (string)
		featureCode (string)
		featureCodeDesc (string)
		featurerCodeAnnounceDate (string date)
		productName (string)
		releaseId (string)
		fixLevel (string)
		externalInfo (string)

Microcode Discovery Service (MDS) as it is also called, is used to determine if microcode installed on your IBM Power Systems is at the latest level. Microcode is a device driver used by Power Systems.

FLRT MDS website:
https://esupport.ibm.com/customercare/mds/

This API requires a *.mup file from your AIX partition, which may be generated using the Inventory Scout tool ( invscout ).

JSON Response example
Download inventoryScoutExample.mup (zipped) , and run the following cURL command after unzipping:

curl -F "[email protected];ype=multipart/form" -H "Expect:" "http//esupport.ibm.com/customercare/mds/mds" -F "format=json"

This sets the filename field to name "mdsData", with format=json in the POST data.

POST http//esupport.ibm.com/customercare/mds/mds

High level JSON structure:

MdsReport (object)
	title (string)
	systems (array of system)
		(system object)
	microcodes (array of microcode)
		(microcode object)

The system object has the following structure:

(system object)
	model (string)
	serial (string)
	hosts (array of host)
		(host object)

The host object has the following structure:

(host object)
	name (string)
	ipAddr (string)
	parId (string)
	aix (string version)
	isService (boolean)
	catalog (object)
		report (string date)
		survey (string date)
	devices (array of device)
		(device object)

The device object has the following structure:

(device object)
	ids (array of strings)
	pkgName (string)
	installed (string version)
	latest (string version)
	recommend (string version)
	errors (array of strings)

The microcode object has the following structure:

(microcode object)
	pkgName (string)
	latest (string version)
	reldate (string date)
	impact (string)
	severity (string)
	download (string url)