Seeking API Developer

Seeking Ivanti (HEAT) Neurons API Developer


  • API Development Experience Ivanti Service Manager (Powered by HEAT) aka Ivanti Neurons for ITSM
  • Attention to detail
  • Self Starter
  • Excellent Communication Skills


  • Configuration of Ivanti Service Manager and Ivanti Asset Manager as per Solution Design Specifications
  • Good understanding of Incident Management, Configuration/Asset Management, CMDB, Business Rules, Workflows, Service Requests, Request Offerings
  • API Development with AAD, DialPad

Apply Here

Ivanti Integration API Flat File Ivanti Project Implementation UK Ireland EU Australia New Zealand Canada US Consultant Developer Freelancer Ivanti Service Manager HEAT Neurons ITSM ITAM

Ivanti Integrations: Flat File or API?

Ivanti Integrations with Ivanti Service Manager (HEAT) aka Ivanti Neurons for ITSM/ITAM are a hot topic.

Since direct database connections are not available with cloud and the majority of customers are in the cloud vs on-premise, the questions is….

Flat File or API?

File-based Integrations have been around for a long time and for that reason are great not only for older and legacy systems but also because they are simply easy to create, maintain, and troubleshoot. Flat files are usually in CSV format, although some of you might remember the pipe delimited HAF files and heat structure files, I believe HSF. These files are scheduled typically daily, hourly, or as needed.

API (Application Program Interfaces) Integrations have been a buzz since they first emerged in 2005. Still a great buzz word thrown around in sales presentations. But are they worth the effort? API integrations require a much greater technical effort to create, maintain, and troubleshoot. Arguably once set up, the API should be easy to support. Key word is “should”.

APIs are secure and real-time. This is a clear advantage, but Flat Files too are secure and can be “near” real-time. Just schedule more-frequently and push flat files for time-sensitive needs such as HR Terminations for example.

Where the lines get blurry is with support, troubleshooting, and compatibility.

Flat files are straight forward, easy to support & troubleshoot, and compatible with legacy systems. Arguably flat files are backward and forward compatible provided the structure doesn’t change. If structure changes on either end of the system (Source, Target) then flat files and APIs need to be updated. Arguably Flat Files win here too because flat files are easy to maintain and support.

But are APIs forward compatible? What if the Application changes? The API changes too. There aren’t any API standards per se across different applications. Applications change, APIs therefor change too and then there are dreaded “bugs” or “features” Something you don’t get with Flat Files. Flat files are based on structure. APIs are code. Development.

Until Codeless Integrations are available, something Ivanti is rumoured to have in the works, the hands down winner for me is Flat File Integrations!

What are your thoughts?

ivanti enhancement request australia uk canada

Reset Internal Authentication Password with Service Desk Manager Role

Recently one of my clients in the UK had an issue where they needed to reset a number of internal HEAT user passwords using the Service Desk Manager role for operations in Singapore.

The challenge was that the “Reset User Password” OOTB quick action and underlying API call can only be run by the Admin role.

The workaround was to add a flag to the employee business object that triggers a workflow to run with a quick action block to call the “Reset User Password” OOTB quick action, which although triggered by the SDM role, would then run using INTERNALSERVICES which has the admin role.