HTTP Event Collector REST API endpoints

The HTTP Event Collector REST API endpoint reference is located in the Splunk Enterprise REST API Reference Manual. Each endpoint has been linked here for your convenience.

REST API endpoint	Description
data/inputs/http	Access or update HTTP Event Collector global configuration tokens and application tokens.
data/inputs/http/{name}	Manage the {name} HTTP Event Collector token. HTTP, as in data/inputs/http/http, indicates global configuration.
data/inputs/http/{name}/disable	Disable the {name} HTTP Event Collector token.
data/inputs/http/{name}/enable	Enable the {name} HTTP Event Collector token.
services/collector	Send events to HTTP Event Collector using the Splunk platform JSON event protocol.
services/collector/ack	Query event indexing status.
services/collector/event	Sends timestamped events to HTTP Event Collector using the Splunk platform JSON event protocol when auto_extract_timestamp is set to "true" in the /event URL. An example of a timestamp is: 2017-01-02 00:00:00. If there is a timestamp in the event's JSON envelope, Splunk honors that timestamp first. If there is no timestamp in the event's JSON envelope, the merging pipeline extracts the timestamp from the event. If "time=xxx" is used in the /event URL then auto_extract_timestamp is disabled..
services/collector/event/1.0	This endpoint works identically to services/collector/event but introduces a protocol version for future scalability.
services/collector/health	Checks the health of HTTP Event Collector. This endpoint is supported in versions 6.6.0+ of Splunk Enterprise.
services/collector/mint	Post MINT formatted data to the HTTP Event Collector.
services/collector/mint/1.0	This endpoint works identically to receivers/token/mint but introduces a protocol version for future scalability.
services/collector/raw	Send raw data directly to the HTTP Event Collector.
services/collector/raw/1.0	This endpoint works identically to services/collector/raw but introduces a protocol version for future scalability.