ServiceDesk Plus
Cloud and on-prem REST v3 ticket investigations, approvals and CMDB over the shared Era estate.
Vendor reference: https://www.manageengine.com/products/service-desk/sdpod-v3-api/getting-started/api-index.html ↗. Machine-readable: compat/servicedesk-plus.json.
Surfaces
| Kind | Path | Notes |
|---|---|---|
| REST | /api/v3 | On-prem; Cloud also uses /app/{portal}/api/v3 |
| MCP | /mcp | API-derived resource and approval tools |
API versions: REST v3
Supported
- Requests, changes, problems, notes, worklogs, approvals, technicians and assets
- input_data envelopes, list_info pagination, field selection, sorting and search criteria
Not supported
- Attachments, projects, releases, purchases and notification delivery
Known differences and test guidance
| Scenario | Difference from ServiceDesk Plus | In your tests |
|---|---|---|
| Writes | REST and MCP writes require a tenant write grant. | Enable writes before creating or updating tickets or approvals. |
| Schema customization | Tenant-specific custom CMDB types and workflow rules are not modeled. | Use the documented resource collections and returned ids. |
Fault injection
| Key | What the client sees |
|---|---|
throttle | Native failure envelope, HTTP 429 and Retry-After. |
fail_next | The next N data-plane requests receive HTTP 429. |
quota_limit | HTTP 429 after the configured request quota. |
error_rate | Native failure envelope with HTTP 500. |
latency_ms | Fixed latency on data-plane requests. |
Applies to every system
- The hosted data plane is read-only: a write is refused with
403 writes_disabled. A SOQL, GraphQL or searchPOSTis a read and is answered. - Faults are injected through
POST /_admin/faultson a simulator you run yourself;POST /_admin/faults/resetclears them. - Rate limits do not happen on their own unless a page says so. Use fault injection to exercise a client's backoff.
- Distributions come from aggregated metadata sketches of data Eon backs up; no customer records; all Era data is simulated.