← Back to Integration
DEVICE MANAGEMENT

Integration with ManageEngine Endpoint Central Integration with SPOG.AI

SPOG.AI integrates with ManageEngine Endpoint Central to provide centralized monitoring, management, and compliance automation for endpoints. By using ManageEngine APIs, the integration retrieves endpoint inventory, patch status, configuration details, and alerts into the SPOG.AI Configuration Management Database (CMDB). This gives IT and security teams a consolidated view of endpoint health, patch posture, configuration compliance, and operational events.

Key Features

CapabilityDescription
Endpoint Asset ManagementBuilds a centralized inventory of managed endpoints and their operating-system and agent details.
Patch MonitoringTracks installed and pending patches to identify exposure and remediation gaps.
Configuration ComplianceRetrieves endpoint policies and configuration details for compliance assessment.
Alert and Event IngestionCollects endpoint alerts and compliance notifications for centralized visibility.
CMDB EnrichmentMaps endpoint data into SPOG.AI CMDB records for operational and security analysis.
Optional Webhook AlertsReceives selected events from Endpoint Central for event-based alerting.

How the Integration Works

SPOG.AI connects to ManageEngine Endpoint Central over HTTPS. On-premises instances authenticate with an Authorization token, while cloud instances use OAuth client credentials and a refresh token. After configuration, SPOG.AI retrieves endpoint inventory, patch information, configuration data, and alerts from the Endpoint Central environment. The collected data enriches the SPOG.AI CMDB and provides actionable insights for IT and security teams. Optional webhooks can send selected endpoint events to SPOG.AI as they occur.

Data Collected

CategoryData CollectedDescription
Endpoint InventoryHostname, operating system, IP address, and agent version for managed devicesEstablishes an inventory of managed endpoints in the SPOG.AI CMDB.
Patch StatusInstalled patches, pending patches, and patch-state detailsSupports patch posture monitoring and identification of remediation gaps.
Configuration DataSystem policies and endpoint configuration detailsSupports configuration compliance monitoring and analysis.
Alerts and EventsEndpoint alerts and compliance notificationsProvides operational visibility and supports incident and alert workflows.

Prerequisites

Before configuring the integration, ensure the following prerequisites are met:

  • ManageEngine Endpoint Central Enterprise edition is deployed and running.
  • Administrator access to both SPOG.AI and ManageEngine Endpoint Central.
  • An Authorization token for an on-premises instance, or OAuth client credentials and a refresh token for a cloud instance.
  • The Endpoint Central users report endpoint required by the current SPOG.AI datasource configuration.
  • HTTPS connectivity from the SPOG Appliance to the Endpoint Central server.
  • Optional: webhooks enabled for event-based alerting.

Configuration

Log in to ManageEngine Endpoint Central

Open the ManageEngine Endpoint Central Web Console and authenticate with an administrator account.

  • Open the ManageEngine Endpoint Central Web Console in your browser.
  • Log in using administrator credentials.

2. Generate an API Key

Create the API key that SPOG.AI will use to access Endpoint Central data.

  • Navigate to Admin → Integrations → API Key Generation.
  • Under the Action column for your username, click Generate.
  • Set Service to Service Desk Plus.
  • Set Expiry to Never Expiry.
  • Set Permissions to Read-only where available, or grant only the access required for the integration.
  • Click Generate to create the API key.
  • Copy the generated key and store it securely. The key will not be shown again.
  • Click Save to finalize the process.

3. Configure Webhooks (Optional)

Configure a webhook if you want ManageEngine events to be sent to SPOG.AI.

  • Go to Admin → Integrations → Webhooks.
  • Click Add Webhook.
  • Webhook URL: Enter the endpoint generated by SPOG.AI.
  • Content Type: Select application/json.
  • Event Triggers: Select the required events, such as patch updates and endpoint alerts.
  • Save the webhook configuration.

4. Configure ManageEngine in SPOG.AI

Add the Endpoint Central connection in SPOG.AI and provide the connection details.

  • Log in to your SPOG.AI account.
  • Navigate to Settings → Integrations → Add Integration.
  • Select ManageEngine Integration and click Configure.
  • Enter the following details:
FieldRequirementDescription
HostMandatoryEndpoint Central base URL or host. This field is required by the datasource configuration.
Instance TypeOptionalUse onprem or cloud. Default: onprem.
AuthorizationConditionalAuthorization token required by the runtime when Instance Type is onprem.
Accounts Base URLConditionalZoho accounts URL used for cloud OAuth. Default: https://accounts.zoho.com. Required by the cloud token flow.
Client IDConditionalOAuth client identifier required for a cloud instance.
Client SecretConditionalOAuth client secret required for a cloud instance. Stored as a password field.
Refresh TokenConditionalOAuth refresh token required for a cloud instance. Stored as a password field.
Customer IDOptionalManageEngine customer identifier used as the customerid query parameter when Data Center Instance is not set.
Data Center InstanceOptionalManageEngine data-center instance. When supplied, it takes precedence over Customer ID.
Enrichment TypesOptionalComma-separated ingestion scopes. Configured default: asset,user. The runtime also supports software and vulnerability scopes.
Fetch UsersOptionalControls user ingestion. Configured default: true.
Users Report EndpointMandatoryEndpoint Central report endpoint used for user or technician data. Required by the current datasource configuration.
Users Report MethodOptionalHTTP method for the users report endpoint. Default: POST.
User Page SizeOptionalNumber of user records requested per page. Default: 400.
User Batch SizeOptionalNumber of user records sent to SPOG.AI per batch. Default: 25.
User Progress EveryOptionalNumber of processed user records between progress updates. Default: 100.
User TimeoutOptionalTimeout for user-report requests, in seconds. Default: 60.
Extra Alias KeysOptionalComma-separated source fields to add as asset aliases.
Log LevelOptionalIntegration logging level. Default: info.

Advanced runtime settings. The appliance code also accepts the following optional settings even though they are not listed in the current standard datasource form.

FieldRequirementDescription
API VersionOptionalAPI version used by BitLocker and software-metering calls. The runtime accepts api_version, bitlocker_api_version, or bitlocker_version; BitLocker v1.4 is enabled when the value is 1.4.
BitLocker Report EndpointOptionalLegacy Endpoint Central report path used to collect BitLocker records when BitLocker API v1.4 is not enabled.
DaysOptionalPositive number of days used to filter computers by last contact.
Software MeteringOptionalEnables collection and publication of Endpoint Central software-metering rules and usage.
Verify SSLOptionalControls TLS certificate verification for ManageEngine remediation requests. Current remediation default: false.
TimeoutOptionalManageEngine remediation request timeout in seconds. Default: 60.
  • Click Save to complete the integration setup.

5. Validate the Integration

Test the connection and confirm that Endpoint Central data is available in SPOG.AI.

  • In SPOG.AI, run Test Connection to validate the configured authentication fields and endpoint accessibility.
  • Confirm that endpoint inventory, patch status, and configuration data appear in the SPOG dashboard.
  • Review ManageEngine audit logs for successful API requests from SPOG.AI.
  • If webhooks are configured, trigger a sample event, such as a patch update, and confirm that SPOG.AI receives it.

Security and Access Control

  • Least Privilege: Assign read-only permissions to API users unless write access is explicitly required.
  • Key Rotation: Rotate API keys periodically; a 90-day rotation interval is recommended.
  • Secure Storage: Store API keys in a vault or secret manager and avoid plaintext storage.
  • Dedicated Account: Use a dedicated integration account instead of a personal administrator account.
  • Revocation: Revoke unused API keys immediately when the integration is no longer active.

Network and Connectivity

  • Firewall Rules: Allow the SPOG Appliance to connect to the ManageEngine server over HTTPS port 443.
  • IP Allowlisting: If proxy or access-control restrictions apply, allowlist the outbound IP ranges of the SPOG Appliance.
  • API Access: Verify that the ManageEngine REST API endpoint is reachable from the appliance network.
  • TLS Requirement: Enforce TLS 1.2 or later between SPOG.AI and ManageEngine.
  • High Availability: Maintain stable connectivity to support consistent data synchronization.

Uninstalling the Integration

  • In SPOG.AI, go to Settings → Integrations and delete the ManageEngine integration entry.
  • In ManageEngine, revoke the API key under Admin → API Key Generation.
  • If configured, delete the webhook under Admin → Integrations → Webhooks.
Frequently Asked Questions