--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # REST API # Set up a REST API integration for Health Log Analytics {#ariaid-title1} * Release version: Yokohama * * Updated July 31, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Set up an integration for streaming log data to your ServiceNow instance for processing by Health Log Analytics. ## Before you begin * Verify that the Health Log Analytics application is installed and provisioned on your instance. For more information, see [Install Health Log Analytics (HLA)](https://servicenow-prod.fluidtopics.net/aoQx9IeZAIRlYKlNd5Fwsw "Install Health Log Analytics by requesting ServiceNow HLA installation from ServiceNow Customer Support."). * Verify that a service instance is available. * Verify that the Health Log Analytics AI Engine is up and running. {#il-connector-hla-rest-api__ul_ugv_1wl_ndc} * Verify that a MID Server is installed and configured with the Log Ingestion capability enabled. For more information, see [MID Server system requirements](https://www.servicenow.com/docs/access?context=r_MIDServerSystemRequirements&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). Important: Health Log Analytics does not support IPv6. To work with the application, configure the MID Server to IPv4. On the MID Web Server Context form, in the Execute on field, select Specific MID Server and not the cluster option. In the MID Server field, select the specific MID Server to which the log data is pulled. * Unless the MID Server and external clients are on the same network, the MID Server must have a public IP address. This is required when its IP is exposed through network address translation (NAT), a load balancer, or a similar device. The public IP address enables external clients, such as Filebeat agents located outside its network, to reach the MID Server. Private IP addresses are not routable over the internet. Without a public IP, external clients cannot connect to the MID Server even if they are configured with its address. In the MID Server properties, add a property named mid.public_ip with the public IP address as the value. For more information, see [Create a MID Server property](https://www.servicenow.com/docs/access?context=r_MIDServerProperties&version=yokohama&pubname=yokohama-servicenow-platform§ion=t_SetMIDServerProperties&ft:locale=en-US). If the MID Server and external clients are on the same network, connections can be made using the private IP address. {#il-connector-hla-rest-api__ul_cmc_lrr_cpb} Note: REST API integrations support only UTF-8 encoding for incoming data. Role required: evt_mgmt_admin ## About this task You set up integrations through the Integrations Launchpad in Service Operations Workspace, which you access from the ITOM AIOps configuration center. The AIOps configuration center is a centralized workspace for configuring and managing AIOps features from a single place. The integrations setup process reduces implementation time compared to manual data input setup in the classic interface in Health Log Analytics. For more information, see [Integrations Launchpad in Service Operations Workspace for ITOM](https://servicenow-prod.fluidtopics.net/Uerz_nc8Z9osqGgNu7LISQ "The Integrations Launchpad showcases all Event Management connector integrations, allowing users to pull or push events from external or internal devices. This centralized hub simplifies Event Management by consolidating integration options in one place."). ## Procedure 1. Navigate to WorkspacesService Operations Workspace. 2. From the bottom of the navigation pane, select the AIOps configuration center icon ![ITOM AIOps configuration center icon](). The ITOM AIOps configuration center page appears. The configuration center is a centralized workspace. Use it to configure and manage AIOps features from a single place. 3. From the Integrate section, under Integrations, select Add integration. The Integrations Launchpad appears. 4. In the Browse integrations tab, enter REST in the search field. 5. Select the REST API integration tile. Note: If you start an integration setup before meeting all prerequisites, a message appears. You can cancel the setup and complete the prior requirements first. Alternatively, you can continue in draft mode and complete the requirements later. Note that you can't activate the integration until you have completed all the prerequisites. 6. On the Provide details form, fill in the fields. For a description of the fields, see [REST API integration configuration fields](https://servicenow-prod.fluidtopics.net/KXomKCo~~LEa~WxBoH4LAg "Description of the fields on the REST API integration configuration forms for Health Log Analytics."). 7. Select Next. 8. In the Set-up instruction screen, copy the provided URL to the clipboard. The format of the URL is: `http://(MID_SERVER_IP):(MID_WEB_SERVER_PORT)/ap1/mid/hla/raw`, where `/aps/mid/hla/raw` is the endpoint. HLA has replaced `(MID_SERVER_IP)` and `(MID_WEB_SERVER_PORT)` with the values you configured on the Provide details form. 9. Do one of the following: * If you completed all the prerequisites before starting the configuration, select Activate. When the integration is activated successfully, the Overview tab is displayed. On the Integrations Launchpad, the integration tile is available in the Installed integrations tab. * If you didn't complete all the prior requirements, select Save draft. The system saves the integration as a draft in the Integrations Launchpad. It appears in the Installed integrations tab, under Waiting for your action. You can complete the prerequisites and activate the integration later. For more information, see [Activate a draft integration in Health Log Analytics](https://servicenow-prod.fluidtopics.net/JOHisk8K5~FoYHdLYY8Bgg "Activate an integration that was configured and saved as a draft in Health Log Analytics (HLA)."). {#il-connector-hla-rest-api__choices_rzd_mll_33c} {#il-connector-hla-rest-api__steps_xsf_z3x_4dc} ## What to do next Instruct your API client to send log messages to the MID Server. 1. In the API client, configure a request with the following parameters: * HTTP Method: POST. * URL: The URL you copied in the Set-up instruction screen. * Authentication: The required authentication credentials. For example, Basic authentication (username and password). Note: The authentication method must be the same as the method configured on the MID Web Server. * Headers: Set the `Content-Type` header to match your payload format. * For JSON: `application/json`. * For raw text: `text/plain`. {#il-connector-hla-rest-api__ul_st2_fjy_fgc} * Body: The logs payload in JSON or raw text. {#il-connector-hla-rest-api__ul_rt2_fjy_fgc} 2. Send the request.A successful response indicates that the MID Server has received the payload. When the MID Server has processed the log messages, the data input streams them to your ServiceNow instance using the REST protocol. {#il-connector-hla-rest-api__ol_fxx_1jy_fgc} *[\>]: and then