CONNECT APP

Build with Splunk HTTP Event Collector

Splunk HTTP Event Collector (HEC) is a fast and efficient way to send data to Splunk Enterprise and Splunk Cloud. Notably, HEC enables you to send data over HTTP (or HTTPS) directly to Splunk Enterprise or Splunk Cloud from your application.

Infrastructure & Cloud

API key

Visit Splunk HTTP Event Collector ↗ Start building

MCP

Give your agent Splunk HTTP Event Collector tools

Every Splunk HTTP Event Collector action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Splunk HTTP Event Collector account for each tool call — you store no tokens.

Pipedream Connect

// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": "{project_id}",
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "splunk_http_event_collector",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// e.g. run Check Splunk HTTP Event Collector Health:
const result = await mcp.callTool({
  name: "splunk_http_event_collector-check-health",
  arguments: {},
})

# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
    "Authorization": f"Bearer {access_token}",
    "x-pd-project-id": "{project_id}",
    "x-pd-environment": "production",
    "x-pd-external-user-id": "{external_user_id}",  # any stable ID for this user in your system
    "x-pd-app-slug": "splunk_http_event_collector",
}

async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
    async with ClientSession(read, write) as session:
        await session.initialize()
        tools = await session.list_tools()

        # e.g. run Check Splunk HTTP Event Collector Health:
        result = await session.call_tool("splunk_http_event_collector-check-health", {})

MCP guide →

API PROXY

Call the Splunk HTTP Event Collector API directly

For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Splunk HTTP Event Collector API with the connected user's credentials attached. You store no tokens and write no refresh logic.

Pipedream Connect

const resp = await pd.proxy.get({
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  accountId: "apn_xxxxxxx",
  url: "https://api.example.com/v1/me",
})

// Any allowed Splunk HTTP Event Collector endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.

# The path segment is the target URL, URL-safe base64 encoded:
# https://api.example.com/v1/me

curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZXhhbXBsZS5jb20vdjEvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
  -H "Authorization: Bearer {access_token}" \
  -H "x-pd-environment: production"

API proxy guide →

SDK

Run Splunk HTTP Event Collector actions from your backend

Connect a user's Splunk HTTP Event Collector account once, then run Check Splunk HTTP Event Collector Health on their behalf from your own code — TypeScript, Python, or plain HTTP.

Pipedream Connect

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "splunk_http_event_collector-check-health",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    splunk_http_event_collector: { authProvisionId: "apn_xxxxxxx" },
  },
})

from pipedream import Pipedream

pd = Pipedream(
    client_id="{oauth_client_id}",
    client_secret="{oauth_client_secret}",
    project_id="{project_id}",
    project_environment="production",
)

result = pd.actions.run(
    id="splunk_http_event_collector-check-health",
    external_user_id="{external_user_id}",  # any stable ID for this user in your system
    configured_props={
        "splunk_http_event_collector": {"authProvisionId": "apn_xxxxxxx"},
    },
)

curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
  -H "Content-Type: application/json" \
  -H "X-PD-Environment: production" \
  -H "Authorization: Bearer {access_token}" \
  -d '{
    "external_user_id": "{external_user_id}",
    "id": "splunk_http_event_collector-check-health",
    "configured_props": {
      "splunk_http_event_collector": { "authProvisionId": "apn_xxxxxxx" }
    }
  }'

Managed auth guide → Tools guide →

TOOLS

Splunk HTTP Event Collector actions

On-demand operations your product or agent can configure and run on behalf of a connected user.

EVENTS

Splunk HTTP Event Collector triggers

Event sources your backend can deploy for users and receive through a webhook.

No Splunk HTTP Event Collector triggers are available yet.

MULTI-APP

Use Splunk HTTP Event Collector with other popular apps

Most products don't stop at one integration. Pair Splunk HTTP Event Collector with the other apps your users rely on, and ship use cases that span both.