Splunk Data Inputs API
Endpoints for configuring and managing data inputs including monitors, TCP/UDP inputs, scripted inputs, and HTTP Event Collector (HEC) tokens. Data inputs define how Splunk ingests data.
Splunk Data Inputs API is one of 14 APIs that Splunk publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 2 JSON Schema definitions.
Tagged areas include Data Inputs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, an API reference, authentication docs, a JSON-LD context, and 2 JSON Schemas.
This API exposes 13 operations across 9 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 9.4.0.
Requests are made against a single base URL, https://{host}:{port}.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Splunk Data Inputs API declares
3 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (BearerAuth).
It accepts HTTP basic authentication (BasicAuth).
An API key is passed in the header as Authorization (HecToken).
By default, every request must be authenticated.
BearerAuth— Splunk authentication token. Obtain a session key by authenticating to /services/auth/login or use a pre-configured bearer token from Settings Tokens in Splunk…BasicAuth— HTTP Basic authentication with a valid Splunk username and password. The credentials are sent as a Base64-encoded string in the Authorization header.HecToken— HTTP Event Collector token. Send as "Splunk " in the Authorization header. Tokens are configured in Splunk Web under Settings Data Inputs HTTP Event Collector.
Paths & Operations 13
Across 9 paths, the API surfaces 13 operations — 1 DELETE, 6 GET, 6 POST. Each is listed below with its method, path, parameters, and response codes.
Endpoints for configuring and managing data inputs including monitors, TCP/UDP inputs, scripted inputs, and HTTP Event Collector (HEC) tokens. Data inputs define how Splunk ingest…
Schemas 15
The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are MonitorInputCreateRequest (10 properties), HecTokenCreateRequest (8 properties), HecEvent (7 properties), MonitorInputUpdateRequest (5 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Splunk 12
Other APIs Splunk publishes across the network.
This is an independent, third-party profile of Splunk Data Inputs API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.