.png)
ManageEngine ServiceDesk Plus Integration Guide
Integrate ServiceDesk Plus with enterprise applications through REST APIs, selected webhook-style notifications, attachment operations, and edition-specific authentication.
ManageEngine ServiceDesk Plus integration options at a glance
ManageEngine ServiceDesk Plus provides REST APIs as its primary integration mechanism for Requests, Users, Technicians, Assets, Changes, Solutions, and other supported resources. Cloud editions generally use OAuth 2.0-style authorization, while on-premises deployments commonly use technician API keys or tokens. Selected editions and configurations can provide webhook-style notifications, although coverage is not universal across objects and events. Attachment operations are available for supported resources, particularly Requests. Martini can orchestrate authenticated API calls, receive applicable callbacks through a REST API, schedule incremental synchronization, map and transform ITSM data, and apply controlled retry, checkpoint, and deduplication logic.
| Integration point | Supported by ManageEngine ServiceDesk Plus? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Create, retrieve, update, and delete supported Requests, Users, Assets, Changes, Solutions, and related resources; add comments, resolutions, notes, worklogs, and associations where supported. | Martini can consume the ServiceDesk Plus REST API from workflows, use environment-specific configuration, map request and response payloads, paginate results, and expose a normalized API to downstream systems. |
| Webhooks / outbound callbacks | Limited | Provide webhook-style notifications for selected automation and notification scenarios, depending on the ServiceDesk Plus edition, configuration, and event type. | Martini can expose a receiving REST API and start a workflow to validate, transform, and route applicable notifications. Unsupported event types can use scheduled REST polling instead. |
| File / attachment APIs | Limited | List, download, add, or delete attachments for supported resources, particularly Requests, subject to API version, permissions, payload, and file-size restrictions. | Martini can retrieve attachment metadata, download or stage file content, transform it when required, and forward it to another application or storage service. |
| Authentication | Yes | ServiceDesk Plus Cloud uses OAuth 2.0-style authorization with data-center-specific endpoints and scopes. On-premises deployments commonly use technician API keys or tokens in HTTP headers. | Martini can use secured environment configuration for OAuth credentials, refresh tokens, API keys, and tokens, with separate values for development, testing, and production. |
| SOAP APIs | Legacy | Older or deployment-specific ServiceDesk Plus installations may expose documented web-service interfaces, but SOAP is not the recommended approach for new integrations. | Martini can consume SOAP services where a target deployment explicitly requires them, while new implementations should prefer the ServiceDesk Plus REST API. |
| Bulk / asynchronous / batch APIs | Not confirmed | A universal bulk or asynchronous API covering all ServiceDesk Plus resources was not confirmed. Larger synchronizations should use pagination, incremental filters, and checkpoints. | Martini can orchestrate bounded batches, preserve checkpoints, control concurrency, and retry transient failures without assuming bulk create or update support. |
| Database / analytics access | Not confirmed | Direct database access is not a general cloud integration mechanism. On-premises reporting or database options require explicit deployment and documentation validation. | Martini can connect to supported databases, but the ServiceDesk Plus application API is preferred to preserve application permissions and reduce schema coupling. |
| GraphQL APIs | Not confirmed | No official ServiceDesk Plus GraphQL API was confirmed in the reviewed material. | Martini should use the confirmed REST API rather than assume GraphQL availability for ServiceDesk Plus. |
How ManageEngine ServiceDesk Plus exposes data and business events
ServiceDesk Plus REST APIs
ServiceDesk Plus REST APIs are the primary integration boundary for supported service desk resources. They provide programmatic access to Requests, Users, Technicians, Assets, Changes, Solutions, and other edition- and version-dependent objects, including selected comments, worklogs, associations, and attachment operations.
Martini implementation pattern
Martini implementation pattern: A workflow authenticates against the appropriate Cloud or on-premises API, sends a request with validated parameters, handles pagination and response status, maps the result into a canonical model, and writes it to the target system. The workflow can also expose a Martini REST API that presents a controlled normalized interface to downstream applications.
Implementation sequence
ServiceDesk Plus Webhook Notifications
ServiceDesk Plus supports webhook-style notifications for selected automation and notification scenarios, but coverage depends on edition, configuration, and event type. These notifications should not be treated as a universal event stream for every object or field.
Martini implementation pattern
Martini implementation pattern: Martini exposes a receiving REST API and associates it with a workflow start trigger. The workflow validates the notification, optionally retrieves the current ServiceDesk Plus resource to avoid relying on incomplete event data, applies deduplication and routing rules, and then updates downstream systems. Scheduled polling covers events without an applicable callback.
Implementation sequence
ServiceDesk Plus Attachments
Attachment operations are available for supported ServiceDesk Plus resources, particularly Requests, but upload and download behavior varies by resource and API version. Integrations should verify multipart handling, URLs, file limits, permissions, and metadata representation.
Martini implementation pattern
Martini implementation pattern: A workflow first processes the parent Request or other supported object, then retrieves attachment metadata and downloads or uploads content using the documented operation. Martini can stage or transform the file before forwarding it, while keeping file errors separate from the parent-object transaction where appropriate.
Implementation sequence
ServiceDesk Plus Scheduled Synchronization
Scheduled synchronization is appropriate when a required ServiceDesk Plus event does not have a supported webhook or callback. REST list operations can be combined with modified-time filters, status filters, object identifiers, pagination, and checkpoints where documented by the target API.
Martini implementation pattern
Martini implementation pattern: A scheduler starts a workflow for a bounded time window. The workflow retrieves pages of Requests, Users, Assets, Changes, or other selected objects, maps and reconciles them, writes successful results, and advances the checkpoint only after the relevant page or window has completed successfully.
Implementation sequence
Common ManageEngine ServiceDesk Plus integration patterns
Pattern 1: Sync Requests to Salesforce Cases
When to use this pattern
Use this pattern when Salesforce handles customer-facing support while ServiceDesk Plus manages internal service desk work. A scheduled workflow or applicable notification can synchronize newly created and updated Requests, with optional status, comment, ownership, and resolution updates in the opposite direction.
Integration direction
Example Mapping
| ManageEngine ServiceDesk Plus Field | Canonical Field | Target Field |
|---|---|---|
| Request.id | sourceRequestId | ServiceDesk Plus Reference |
| Request.subject | serviceSummary | Case Subject |
| Request.priority | priority | Case Priority |
| Request.status | serviceStatus | Case Status |
Martini implementation pattern
Martini receives or retrieves eligible Requests, resolves the requester and correlation key, maps ServiceDesk Plus statuses and priorities to Salesforce values, and checks for an existing Case before creating one. Updates use the stored relationship and explicit ownership rules; transient API failures are retried, while validation and permission errors are routed for review.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- error handling
- scheduled synchronization
Pattern 2: Create onboarding Requests from Workday
When to use this pattern
Use this pattern to initiate IT fulfillment when Workday reports a new worker, department transfer, location change, or termination. The workflow creates a standardized ServiceDesk Plus Request or onboarding task only when required worker attributes and employment conditions are present.
Integration direction
Example Mapping
| ManageEngine ServiceDesk Plus Field | Canonical Field | Target Field |
|---|---|---|
| Worker.workerId | externalWorkerId | Request external reference |
| Worker.startDate | startDate | Request due or planned date |
| Worker.department | department | Request department |
| Worker.manager | manager | Request requester or approval context |
Martini implementation pattern
Martini retrieves or receives eligible Workday changes, validates department, manager, location, and employment status, applies request-template and equipment rules, and submits the ServiceDesk Plus Request through its REST API. A correlation identifier prevents duplicate onboarding requests, and incomplete worker data is sent to an exception path rather than retried indefinitely.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- validation
- error handling
Pattern 3: Coordinate Changes with Jira
When to use this pattern
Use this pattern when development or platform teams execute work in Jira while IT governance and approvals remain in ServiceDesk Plus Changes. Approved Changes can create Jira issues, while implementation status, comments, and completion information can be returned to ServiceDesk Plus.
Integration direction
Example Mapping
| ManageEngine ServiceDesk Plus Field | Canonical Field | Target Field |
|---|---|---|
| Change.id | changeId | Jira external reference |
| Change.title | changeSummary | Jira Summary |
| Change.status | changeState | Jira Status |
| Change.implementation_plan | implementationPlan | Jira Description |
Martini implementation pattern
A Martini workflow detects approved Changes through applicable notifications or scheduled retrieval, creates or updates the corresponding Jira issue, and stores both identifiers. State translation and field ownership rules prevent update loops; retries are limited to safe operations, and conflicts or unsupported status values are recorded for reconciliation.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- correlation management
- error handling
Pattern 4: Reconcile Assets and Users with ServiceNow
When to use this pattern
Use this pattern when an organization operates both ServiceDesk Plus and ServiceNow and needs controlled synchronization of selected Assets, Users, and Requests. It is most appropriate when ownership is explicitly assigned by object or field rather than allowing unrestricted bidirectional updates.
Integration direction
Example Mapping
| ManageEngine ServiceDesk Plus Field | Canonical Field | Target Field |
|---|---|---|
| Asset.id | sourceAssetId | ServiceNow Configuration Item reference |
| Asset.name | assetName | Configuration Item Name |
| User.email | userEmail | User Email |
| Request.status | requestStatus | ServiceNow Incident State |
Martini implementation pattern
Martini retrieves incremental ServiceDesk Plus data, resolves target identifiers, applies ownership and reconciliation rules, and updates ServiceNow only for approved fields. Checkpoints, stable external keys, validation, and exception queues support repeatable synchronization without creating duplicate Assets, Users, or Requests.
Martini capabilities used
- scheduled synchronization
- API consumption
- data mapping
- business rules
- checkpointing
- error handling
Applications commonly integrated with ManageEngine ServiceDesk Plus
ServiceDesk Plus can be integrated with adjacent enterprise applications when organizations need to coordinate service requests, changes, assets, identities, employee lifecycle events, or operational notifications. These relationships require validation against the relevant application APIs, permissions, and ServiceDesk Plus edition.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize customer support cases, account information, and service requests with ServiceDesk Plus Requests. | Salesforce → Martini → ManageEngine ServiceDesk Plus | Martini consumes Salesforce and ServiceDesk Plus APIs, maintains cross-system identifiers, maps case and request states, and applies duplicate detection before creating or updating records. |
| ServiceNow | Reconcile service desk, asset, change, or request data where both platforms operate in the same enterprise. | ManageEngine ServiceDesk Plus → Martini → ServiceNow | A Martini workflow synchronizes selected Assets, Users, Requests, and Changes according to field-ownership rules, using reconciliation checkpoints and exception handling for conflicts. |
| Jira | Coordinate development work, defects, and change implementation tasks with ServiceDesk Plus Changes and Requests. | ManageEngine ServiceDesk Plus → Martini → Jira | Martini maps approved Changes or selected Requests to Jira issues, stores correlation identifiers, translates statuses and comments, and performs idempotent bidirectional updates. |
| Workday | Start onboarding and offboarding workflows from worker, department, manager, location, and employment-status changes. | Workday → Martini → ManageEngine ServiceDesk Plus | Martini retrieves or receives eligible Workday changes, validates required worker attributes, applies request-template rules, and creates ServiceDesk Plus Requests or onboarding tasks through the REST API. |
| Microsoft Entra ID | Reconcile user and group-related information for ServiceDesk Plus requesters and technicians, subject to deployment and permission constraints. | Microsoft Entra ID → Martini → ManageEngine ServiceDesk Plus | A scheduled Martini workflow compares identity data with ServiceDesk Plus Users, applies scope and ownership rules, and updates only fields supported by the target edition and API permissions. |
| Microsoft Teams | Publish selected request, incident, approval, or change notifications to an enterprise collaboration channel. | ManageEngine ServiceDesk Plus → Martini → Microsoft Teams | Martini polls or receives applicable ServiceDesk Plus notifications, formats a concise message from the Request or Change payload, and sends it to the Teams integration endpoint with controlled failure handling. |
| NetSuite | Coordinate employee, customer, asset, or service-related information where NetSuite is an operational system. | NetSuite → Martini → ManageEngine ServiceDesk Plus | Martini orchestrates API calls in both systems, maps only validated business objects, maintains external identifiers, and routes unsupported or ambiguous data to an exception process. |
| Slack | Send selected incident, approval, or change notifications to operational channels. | ManageEngine ServiceDesk Plus → Martini → Slack | A Martini workflow retrieves eligible ServiceDesk Plus events or changes, applies notification rules, and publishes normalized messages while preventing repeated notifications through a stored event key. |
How to build a ManageEngine ServiceDesk Plus integration in Martini
Objective
Establish the target ServiceDesk Plus deployment model before building workflows, including Cloud or on-premises edition, data center or base URL, API version, scopes, technician permissions, and available modules.
Instructions in Martini
- Choose OAuth 2.0-style authorization for ServiceDesk Plus Cloud where applicable
- Use a technician API key or token for supported on-premises deployments
- Store credentials and tokens as environment-specific Martini secrets
- Confirm permissions for each selected object and operation
Objective
Select an event-driven, scheduled, or API-led entry point based on the ServiceDesk Plus capability available for the required object and event.
Instructions in Martini
- Use a Martini REST API and start trigger for an applicable ServiceDesk Plus callback
- Use a scheduler when webhook coverage is unavailable or incomplete
- Define bounded synchronization windows and incremental filters
- Document whether the workflow is one-way or bidirectional
Objective
Retrieve current ServiceDesk Plus data rather than relying on incomplete notifications, and process list responses with pagination and checkpoints.
Instructions in Martini
- Call the appropriate ServiceDesk Plus REST resource
- Handle pagination explicitly
- Retrieve related Users, Technicians, Assets, or attachments when required
- Persist the last successful checkpoint only after processing succeeds
Objective
Coordinate API calls, lookups, transformations, target writes, and exception paths in a maintainable Martini workflow.
Instructions in Martini
- Separate authentication, retrieval, mapping, business rules, and target writes into clear workflow stages
- Use correlation identifiers for parent and related objects
- Route validation, permission, rate-limit, and transient failures differently
- Keep edition-specific API behavior in configuration or reusable integration logic
Objective
Convert ServiceDesk Plus payloads and enumerations into the target system's canonical and application-specific model.
Instructions in Martini
- Map actual objects such as Requests, Users, Assets, Changes, and Solutions
- Translate statuses, priorities, categories, impact, urgency, and approval states explicitly
- Handle custom fields, sites, departments, and templates through configurable mappings
- Process attachments as separate file operations where required
Objective
Apply ownership, deduplication, eligibility, and security rules before creating or updating data in either system.
Instructions in Martini
- Search for an existing external reference before non-idempotent creates
- Apply request, onboarding, change, notification, or reconciliation conditions
- Restrict updates to fields owned by the integration
- Reject incomplete or unauthorized payloads before submission
Common ManageEngine ServiceDesk Plus data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Requests | Represent service requests, incidents, comments, resolutions, assignments, statuses, and related service desk activity. | Salesforce, Jira, Workday, ServiceNow, Microsoft Teams, Slack | Martini retrieves or creates Requests through REST workflows, maps requester, priority, status, category, and ownership fields, applies correlation rules, and separately processes supported attachments or worklogs. |
| Users | Represent requesters and other people associated with service desk activity. | Microsoft Entra ID, Workday, ServiceNow, Salesforce | Martini synchronizes approved identity attributes, validates site and department relationships, and respects technician, role, and visibility permissions. |
| Technicians | Represent service desk agents responsible for Requests and other ITSM work. | Microsoft Entra ID, ServiceNow | Martini can reconcile supported technician attributes where the edition and permissions allow it, while keeping credentials and authorization data in environment secrets. |
| Assets | Represent hardware, software, and other configuration or inventory items associated with service operations. | ServiceNow, NetSuite, Microsoft Entra ID | Martini synchronizes selected asset attributes with explicit ownership rules, incremental checkpoints, and validation for site, user, and department references. |
| Changes | Represent planned changes with approval, implementation, and review information. | Jira, ServiceNow, Microsoft Teams, Slack | Martini maps approved Changes to external work items or notifications, translates lifecycle states, stores correlation identifiers, and handles conflicts idempotently. |
| Solutions | Represent knowledge articles and reusable resolutions for service desk teams. | Confluence, ServiceNow | Martini can retrieve and transform supported Solutions through the REST API, applying content, status, ownership, and publication rules before writing to a target knowledge system. |
Authentication and security considerations
Edition-specific authentication
ServiceDesk Plus Cloud generally uses OAuth 2.0-style authorization with a registered client, data-center-specific endpoints, scopes, and access or refresh tokens. On-premises deployments commonly use technician API keys or tokens in HTTP headers. The exact method depends on the edition and API version.
Least-privilege access
Permissions are governed by technician roles, application permissions, site or department access, asset and request visibility, and Cloud OAuth scopes. Configure identities with only the access required by the integration.
Secret handling
- Store client secrets, refresh tokens, API keys, and technician tokens as environment-specific Martini secrets.
- Maintain separate credentials for development, testing, and production.
- Do not embed credentials in workflow mappings or log authorization headers and sensitive payload content.
Operational considerations for ManageEngine ServiceDesk Plus integrations
Deployment and schema differences
Confirm whether the target is ServiceDesk Plus Cloud or on-premises, together with the data center or base URL, API version, enabled modules, permissions, and supported fields. Custom fields, templates, sites, departments, and enumerations should be configuration-driven.
Pagination and throttling
Process list responses page by page and preserve checkpoints. Use bounded concurrency, retry delays, and exponential backoff for HTTP 429 and transient server errors. Do not assume a default response contains all Requests, Users, Assets, or Changes.
Idempotency and synchronization
Maintain cross-references between ServiceDesk Plus identifiers and external identifiers. Search for an existing correlation key before non-idempotent creates, define field ownership for bidirectional flows, and advance checkpoints only after successful processing.
Attachments and errors
Verify attachment payload format, size, content type, permissions, and whether operations are separate from the parent object. Capture HTTP status, ServiceDesk Plus error information, request identifiers, and response details in controlled logs while separating retryable failures from validation and permission errors.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration beyond a script
Martini provides a maintainable workflow layer for authenticated API calls, webhook reception, scheduled synchronization, pagination, checkpoints, transformations, business rules, and target-system writes. This avoids embedding the entire integration lifecycle in a one-off script.
Reusable integration assets
Teams can expose a controlled Martini REST API, reuse workflow logic, isolate Cloud and on-premises configuration, and maintain canonical mappings for Requests, Users, Assets, Changes, and related objects.
Operational control
- Apply explicit retry, deduplication, validation, and exception handling rules.
- Monitor workflow execution and retain useful processing metadata without exposing secrets.
- Adapt mappings when ServiceDesk Plus editions, API versions, custom fields, or target schemas differ.
Frequently asked questions
ServiceDesk Plus is primarily integrated through its REST APIs for Requests, Users, Technicians, Assets, Changes, Solutions, and other supported resources. Selected editions and configurations can provide webhook-style notifications, while scheduled REST polling supports events without applicable callbacks. Cloud and on-premises editions require different deployment, authentication, URL, and API-version considerations.
Yes. Martini can consume the ServiceDesk Plus REST API, use OAuth 2.0-style authorization for supported Cloud deployments, use technician API keys or tokens for supported on-premises deployments, receive applicable webhook-style notifications, process attachments, and orchestrate mappings, synchronization, validation, and error handling.
No. A dedicated ServiceDesk Plus connector is not required. Martini can integrate using the vendor's confirmed REST APIs, applicable webhook-style callbacks, attachment operations, and edition-specific authentication mechanisms.
Lonti does not charge an additional per-connector or per-vendor fee to integrate ServiceDesk Plus. Integrations are subject to the provisioned capacity of the Martini environment. Separate costs may apply from ManageEngine, infrastructure providers, or other third-party systems based on subscriptions, usage, and deployment model.
REST APIs are the recommended primary method for new integrations. Use webhook-style notifications only for events supported by the target edition and configuration, and use scheduled polling with pagination and checkpoints for other events. SOAP is a legacy or deployment-specific option and should not be selected unless a required service is explicitly documented.
ServiceDesk Plus supports webhook-style notifications for selected automation and notification scenarios, but coverage is edition-, configuration-, and event-dependent. They should not be treated as a universal event stream. Martini can receive applicable callbacks through a REST API; unsupported events can use scheduled REST polling.
Martini workflows retrieve or receive ServiceDesk Plus objects, map them to a canonical model, translate statuses and enumerations, apply business rules, and write to target applications. Pagination, incremental filters, checkpoints, stable external references, and explicit field-ownership rules support reliable one-way or bidirectional synchronization.
Martini can distinguish authentication, permission, validation, rate-limit, and transient server failures and apply appropriate retry behavior. Workflows can use bounded concurrency, exponential backoff, correlation identifiers, idempotent update logic, and controlled logging. Non-idempotent creates should not be retried blindly.
Related Martini documentation
ServiceDesk APIs
Data Processing
Connect ManageEngine ServiceDesk Plus with Martini
Use Martini to build maintainable ServiceDesk Plus integrations around REST APIs, selected webhook-style notifications, secure authentication, workflow orchestration, data mapping, synchronization, and operational controls.