Integrate ManageEngine with ServiceDesk Plus

Check the Prerequisites First

The integration itself takes minutes — the failures almost always come from skipping these checks. You need administrator access on both products: the ServiceDesk Plus side runs under a technician account with SDAdmin privileges for its API key, so plan whose account that will be.

The two servers must be able to reach each other by server name, port and protocol. If one runs on HTTPS with a certificate the other does not trust, the handshake fails — fix reachability before touching any keys. On multi-site setups, the site and office naming and the computer hierarchy should also line up between the two products, or assets land in the wrong place.

Generate the Endpoint Central API Key

Authentication between the two servers is handled by API keys in both directions — one key per direction. Start on the Endpoint Central side: log in to the Endpoint Central console with an administrator account and generate the API key for the ServiceDesk Plus integration.

Copy the key somewhere safe for the next step. This key is what proves to ServiceDesk Plus that the data arriving really comes from your Endpoint Central server.

Enter the Endpoint Central Details in ServiceDesk Plus

Now tell ServiceDesk Plus where Endpoint Central lives. Log in to ServiceDesk Plus with admin credentials and open the Endpoint Central server settings (under Admin, Endpoint Central Server Settings).

Enter the server name, port number and communication protocol — HTTP or HTTPS, matching how your Endpoint Central server actually runs — and paste the API key you generated in Endpoint Central. Then choose the features to integrate — asset data, help desk requests, software deployment and the rest — instead of switching everything on blindly, and Save.

ServiceDesk Plus now knows your endpoint server and can authenticate to it: hardware and software inventory can flow into the asset module, and users can raise tickets from the Endpoint Central agent icon on their own PC with the machine details attached.

Generate the ServiceDesk Plus API Key

Half done — and this is the half people forget. Communication from ServiceDesk Plus to Endpoint Central needs its own key, generated in ServiceDesk Plus and stored in Endpoint Central.

In ServiceDesk Plus, go to Admin → Users → Technicians. Edit an existing technician or add a new one for the integration, enable login for the technician and give it administrator (SDAdmin) privileges. Under API key details, generate the API key and copy it.

Then switch to the Endpoint Central console: Admin → Integrations → ServiceDesk Plus settings. Enter the ServiceDesk Plus server details, paste the copied API key and Save. Both directions are now authenticated.

Turn On the Endpoint Central Menu for Technicians

Asset data syncing is only half the prize. For technicians to act from inside tickets, enable the UI integration. In ServiceDesk Plus, click the gear icon at the top right and go to Apps and Add-ons → Integrations → Endpoint Central. Confirm the Endpoint Central server name, port and protocol, and tick the checkbox to enable the Endpoint Central menu.

Then enable it per technician: Users → Technicians → edit the technician → tick Enable to access Desktop and MDM Plugin Functionality → Save. Technicians then see the machine inside the ticket — hardware, software and patch status — and can start a remote session, deploy or remove software, and open system tools on that exact machine without leaving the ticket.

Verify the Integration

Do not declare success because the settings saved — prove it with the three checks that matter. Inventory check: confirm a known computer's hardware and software details now appear inside ServiceDesk Plus assets; inventory syncs immediately when it is working. Ticket check: raise a test ticket from a PC's agent icon and confirm it arrives in ServiceDesk Plus with the machine attached. Action check: from that ticket, run one harmless action — open the machine's system details — and confirm it responds.

Keep the API Keys Safe

The integration runs under these two keys day and night, across your whole endpoint fleet and your help desk. Generate them under the dedicated integration account, paste them only into the two consoles, and keep them out of tickets, emails and screenshots.