Extended observability: pushing API logs to Splunk
November 19, 2026
Unified.to can send detailed API call logs to Splunk through Splunk's HTTP Event Collector (HEC). These are the same logs you can already send to Datadog, Grafana / Loki, ClickHouse and a syslog server; you choose one destination in your workspace settings. Log streaming is available on the Pro and Scale plans, and only workspace admins can change it.
What you need from Splunk
You need an HTTP Event Collector URL and an HEC token from your Splunk deployment, and the HEC endpoint needs a TLS certificate from a public certificate authority. The index is optional: leave it blank and Splunk writes to the token's default index.
- Splunk Cloud Platform: create a token as described in Set up and use HTTP Event Collector in Splunk Web for Splunk Cloud Platform.
- Splunk Enterprise: enable HEC in its Global Settings, turn on SSL so it accepts HTTPS with a certificate from a public certificate authority (see below), and create a token as described in Set up and use HTTP Event Collector in Splunk Web for Splunk Enterprise.
- If you plan to set an index, make sure it exists and the token is allowed to write to it.
How do you connect Splunk in Unified.to?
Open Workspace settings, find External logging, and choose Splunk as the logging service. Then fill in:
| Field | What to enter |
|---|---|
| HTTP Event Collector URL | Your HEC base URL with no path, for example https://http-inputs-acme.splunkcloud.com. Unified.to adds /services/collector/event itself, replacing any path you paste. The URL must start with https://; https:// URLs are rejected |
| HEC token | The HEC token you created in Splunk |
| Index | Optional. The Splunk index to write to, for example main. Leave it blank to use the token's default index |
| Save the settings. |
Which HEC URL should you enter?
Enter the scheme, host and, where needed, port, and stop there. Splunk documents these HEC hosts:
- Splunk Cloud Platform on AWS:
https://http-inputs-your-stack.splunkcloud.com, on port 443 - Splunk Cloud Platform on Google Cloud or Azure:
https://http-inputs.your-stack.splunkcloud.com, with a dot afterhttp-inputsinstead of a hyphen - Splunk Cloud Platform free trial: the
http-inputs-host on port 8088, for examplehttps://http-inputs-your-stack.splunkcloud.com:8088; check that it presents a certificate from a public certificate authority before you connect (see below) - Splunk Enterprise: your own host and HEC port, which is 8088 unless your administrator changed it, for example
https://splunk.example.com:8088
Splunk notes that leaving out the http-inputs prefix on Splunk Cloud Platform stops data reaching HEC.
Unified.to verifies the HEC endpoint's TLS certificate against public certificate authorities, and there is no option for self-signed certificates or a custom CA. Splunk Enterprise's default HEC certificate isn't issued by a public CA, so install one that is before you connect.
How do you check that logs are arriving?
Make a test call to the Unified API, for example by listing an object on one of your connections, or trigger a webhook delivery (logs cover both API calls and webhook calls), then search the index you entered in Splunk, for example index=main. Each Unified API call should appear as an event.
If nothing arrives, check that:
- the HEC URL is reachable from the internet and starts with
https:// - the host uses the right
http-inputsform for your Splunk Cloud Platform deployment - the token is enabled, and any index you entered exists and is one the token is allowed to write to
- on Splunk Enterprise, HEC is enabled in Global Settings with SSL on
- the HEC endpoint's certificate is issued by a public certificate authority; self-signed and private-CA certificates are rejected