This page documents all of the API endpoints for each Druid service type.
The following endpoints are supported by all nodes.
/statusReturns the Druid version, loaded extensions, memory used, total memory and other useful information about the node.
/status/healthAn endpoint that always returns a boolean “true” value with a 200 OK response, useful for automated health checks.
/status/propertiesReturns the current configuration properties of the node.
/druid/coordinator/v1/leaderReturns the current leader coordinator of the cluster.
/druid/coordinator/v1/isLeaderReturns true if the coordinator receiving the request is the current leader.
Returns a JSON object with field “leader”, either true or false, indicating if this server is the current leader coordinator of the cluster. In addition, returns HTTP 200 if the server is the current leader and HTTP 404 if not. This is suitable for use as a load balancer status check if you only want the active leader to be considered in-service at the load balancer.
/druid/coordinator/v1/loadstatusReturns the percentage of segments actually loaded in the cluster versus segments that should be loaded in the cluster.
/druid/coordinator/v1/loadstatus?simpleReturns the number of segments left to load until segments that should be loaded in the cluster are available for queries. This does not include replication.
/druid/coordinator/v1/loadstatus?fullReturns the number of segments left to load in each tier until segments that should be loaded in the cluster are all available. This includes replication.
/druid/coordinator/v1/loadqueueReturns the ids of segments to load and drop for each historical node.
/druid/coordinator/v1/loadqueue?simpleReturns the number of segments to load and drop, as well as the total segment load and drop size in bytes for each historical node.
/druid/coordinator/v1/loadqueue?fullReturns the serialized JSON of segments to load and drop for each historical node.
/druid/coordinator/v1/metadata/datasourcesReturns a list of the names of enabled datasources in the cluster.
/druid/coordinator/v1/metadata/datasources?includeDisabledReturns a list of the names of enabled and disabled datasources in the cluster.
/druid/coordinator/v1/metadata/datasources?fullReturns a list of all enabled datasources with all metadata about those datasources as stored in the metadata store.
/druid/coordinator/v1/metadata/datasources/{dataSourceName}Returns full metadata for a datasource as stored in the metadata store.
/druid/coordinator/v1/metadata/datasources/{dataSourceName}/segmentsReturns a list of all segments for a datasource as stored in the metadata store.
/druid/coordinator/v1/metadata/datasources/{dataSourceName}/segments?fullReturns a list of all segments for a datasource with the full segment metadata as stored in the metadata store.
/druid/coordinator/v1/metadata/datasources/{dataSourceName}/segments/{segmentId}Returns full segment metadata for a specific segment as stored in the metadata store.
/druid/coordinator/v1/metadata/datasources/{dataSourceName}/segmentsReturns a list of all segments, overlapping with any of given intervals, for a datasource as stored in the metadata store. Request body is array of string intervals like [interval1, interval2,...] for example [“2012-01-01T00:00:00.000/2012-01-03T00:00:00.000”, “2012-01-05T00:00:00.000/2012-01-07T00:00:00.000”]
/druid/coordinator/v1/metadata/datasources/{dataSourceName}/segments?fullReturns a list of all segments, overlapping with any of given intervals, for a datasource with the full segment metadata as stored in the metadata store. Request body is array of string intervals like [interval1, interval2,...] for example [“2012-01-01T00:00:00.000/2012-01-03T00:00:00.000”, “2012-01-05T00:00:00.000/2012-01-07T00:00:00.000”]
/druid/coordinator/v1/datasourcesReturns a list of datasource names found in the cluster.
/druid/coordinator/v1/datasources?simpleReturns a list of JSON objects containing the name and properties of datasources found in the cluster. Properties include segment count, total segment byte size, minTime, and maxTime.
/druid/coordinator/v1/datasources?fullReturns a list of datasource names found in the cluster with all metadata about those datasources.
/druid/coordinator/v1/datasources/{dataSourceName}Returns a JSON object containing the name and properties of a datasource. Properties include segment count, total segment byte size, minTime, and maxTime.
/druid/coordinator/v1/datasources/{dataSourceName}?fullReturns full metadata for a datasource .
/druid/coordinator/v1/datasources/{dataSourceName}/intervalsReturns a set of segment intervals.
/druid/coordinator/v1/datasources/{dataSourceName}/intervals?simpleReturns a map of an interval to a JSON object containing the total byte size of segments and number of segments for that interval.
/druid/coordinator/v1/datasources/{dataSourceName}/intervals?fullReturns a map of an interval to a map of segment metadata to a set of server names that contain the segment for that interval.
/druid/coordinator/v1/datasources/{dataSourceName}/intervals/{interval}Returns a set of segment ids for an ISO8601 interval. Note that {interval} parameters are delimited by a _ instead of a / (e.g., 2016-06-27_2016-06-28).
/druid/coordinator/v1/datasources/{dataSourceName}/intervals/{interval}?simpleReturns a map of segment intervals contained within the specified interval to a JSON object containing the total byte size of segments and number of segments for an interval.
/druid/coordinator/v1/datasources/{dataSourceName}/intervals/{interval}?fullReturns a map of segment intervals contained within the specified interval to a map of segment metadata to a set of server names that contain the segment for an interval.
/druid/coordinator/v1/datasources/{dataSourceName}/intervals/{interval}/serverviewReturns a map of segment intervals contained within the specified interval to information about the servers that contain the segment for an interval.
/druid/coordinator/v1/datasources/{dataSourceName}/segmentsReturns a list of all segments for a datasource in the cluster.
/druid/coordinator/v1/datasources/{dataSourceName}/segments?fullReturns a list of all segments for a datasource in the cluster with the full segment metadata.
/druid/coordinator/v1/datasources/{dataSourceName}/segments/{segmentId}Returns full segment metadata for a specific segment in the cluster.
/druid/coordinator/v1/datasources/{dataSourceName}/tiersReturn the tiers that a datasource exists in.
/druid/coordinator/v1/datasources/{dataSourceName}Enables all segments of datasource which are not overshadowed by others.
/druid/coordinator/v1/datasources/{dataSourceName}/segments/{segmentId}Enables a segment of a datasource.
/druid/coordinator/v1/datasources/{dataSourceName}Disables a datasource.
/druid/coordinator/v1/datasources/{dataSourceName}/intervals/{interval}@Deprecated. /druid/coordinator/v1/datasources/{dataSourceName}?kill=true&interval={myISO8601Interval}Runs a Kill task for a given interval and datasource.
Note that {interval} parameters are delimited by a _ instead of a / (e.g., 2016-06-27_2016-06-28).
/druid/coordinator/v1/datasources/{dataSourceName}/segments/{segmentId}Disables a segment.
/druid/coordinator/v1/rulesReturns all rules as JSON objects for all datasources in the cluster including the default datasource.
/druid/coordinator/v1/rules/{dataSourceName}Returns all rules for a specified datasource.
/druid/coordinator/v1/rules/{dataSourceName}?fullReturns all rules for a specified datasource and includes default datasource.
/druid/coordinator/v1/rules/history?interval=<interval>Returns audit history of rules for all datasources. default value of interval can be specified by setting druid.audit.manager.auditHistoryMillis (1 week if not configured) in coordinator runtime.properties
/druid/coordinator/v1/rules/history?count=<n>Returns last entries of audit history of rules for all datasources.
/druid/coordinator/v1/rules/{dataSourceName}/history?interval=<interval>Returns audit history of rules for a specified datasource. default value of interval can be specified by setting druid.audit.manager.auditHistoryMillis (1 week if not configured) in coordinator runtime.properties
/druid/coordinator/v1/rules/{dataSourceName}/history?count=<n>Returns last entries of audit history of rules for a specified datasource.
/druid/coordinator/v1/rules/{dataSourceName}POST with a list of rules in JSON form to update rules.
Optional Header Parameters for auditing the config change can also be specified.
| Header Param Name | Description | Default |
|---|---|---|
X-Druid-Author | author making the config change | "" |
X-Druid-Comment | comment describing the change being done | "" |
Note that {interval} parameters are delimited by a _ instead of a / (e.g., 2016-06-27_2016-06-28).
/druid/coordinator/v1/intervalsReturns all intervals for all datasources with total size and count.
/druid/coordinator/v1/intervals/{interval}Returns aggregated total size and count for all intervals that intersect given isointerval.
/druid/coordinator/v1/intervals/{interval}?simpleReturns total size and count for each interval within given isointerval.
/druid/coordinator/v1/intervals/{interval}?fullReturns total size and count for each datasource for each interval within given isointerval.
/druid/coordinator/v1/config/compactionReturns all compaction configs.
/druid/coordinator/v1/config/compaction/{dataSource}Returns a compaction config of a dataSource.
/druid/coordinator/v1/config/compaction/taskslots?ratio={someRatio}&max={someMaxSlots}Update the capacity for compaction tasks. ratio and max are used to limit the max number of compaction tasks. They mean the ratio of the total task slots to the copmaction task slots and the maximum number of task slots for compaction tasks, respectively. The actual max number of compaction tasks is min(max, ratio * total task slots). Note that ratio and max are optional and can be omitted. If they are omitted, default values (0.1 and unbounded) will be set for them.
/druid/coordinator/v1/config/compactionCreates or updates the compaction config for a dataSource. See Compaction Configuration for configuration details.
/druid/coordinator/v1/config/compaction/{dataSource}Removes the compaction config for a dataSource.
/druid/coordinator/v1/serversReturns a list of servers URLs using the format {hostname}:{port}. Note that nodes that run with different types will appear multiple times with different ports.
/druid/coordinator/v1/servers?simpleReturns a list of server data objects in which each object has the following keys:
host: host URL include ({hostname}:{port})type: node type (indexer-executor, historical)currSize: storage size currently usedmaxSize: maximum storage sizeprioritytier/druid/indexer/v1/leaderReturns the current leader overlord of the cluster. If you have multiple overlords, just one is leading at any given time. The others are on standby.
/druid/indexer/v1/isLeaderThis returns a JSON object with field “leader”, either true or false. In addition, this call returns HTTP 200 if the server is the current leader and HTTP 404 if not. This is suitable for use as a load balancer status check if you only want the active leader to be considered in-service at the load balancer.
/druid/indexer/v1/task/{taskId}/statusRetrieve the status of a task.
/druid/indexer/v1/task/{taskId}/segmentsRetrieve information about the segments of a task.
/druid/indexer/v1/task/{taskId}/reportsRetrieve a task completion report for a task. Only works for completed tasks.
/druid/indexer/v1/taskEndpoint for submitting tasks and supervisor specs to the overlord. Returns the taskId of the submitted task.
druid/indexer/v1/task/{taskId}/shutdownShuts down a task.
druid/indexer/v1/datasources/{dataSource}/shutdownAllTasksShuts down all tasks for a dataSource.
The MiddleManager does not have any API endpoints beyond the common endpoints.
/druid/worker/v1/chat/{taskId}/rowStatsRetrieve a live row stats report from a peon. See task reports for more details.
/druid/worker/v1/chat/{taskId}/unparseableEventsRetrieve an unparseable events report from a peon. See task reports for more details.
/druid/v2/datasourcesReturns a list of queryable datasources.
/druid/v2/datasources/{dataSourceName}Returns the dimensions and metrics of the datasource. Optionally, you can provide request parameter “full” to get list of served intervals with dimensions and metrics being served for those intervals. You can also provide request param “interval” explicitly to refer to a particular interval.
If no interval is specified, a default interval spanning a configurable period before the current time will be used. The duration of this interval is specified in ISO8601 format via:
druid.query.segmentMetadata.defaultHistory
/druid/v2/datasources/{dataSourceName}/dimensionsReturns the dimensions of the datasource.
/druid/v2/datasources/{dataSourceName}/metricsReturns the metrics of the datasource.
/druid/v2/datasources/{dataSourceName}/candidates?intervals={comma-separated-intervals-in-ISO8601-format}&numCandidates={numCandidates}Returns segment information lists including server locations for the given datasource and intervals. If “numCandidates” is not specified, it will return all servers for each interval.
/druid/broker/v1/loadstatusReturns a flag indicating if the broker knows about all segments in Zookeeper. This can be used to know when a broker node is ready to be queried after a restart.
/druid/v2/The endpoint for submitting queries. Accepts an option ?pretty that pretty prints the results.
/druid/v2/candidates/Returns segment information lists including server locations for the given query..
/druid/historical/v1/loadstatusReturns JSON of the form {"cacheInitialized":<value>}, where value is either true or false indicating if all segments in the local cache have been loaded. This can be used to know when a historical node is ready to be queried after a restart.
/druid/historical/v1/readinessSimilar to /druid/historical/v1/loadstatus, but instead of returning JSON with a flag, responses 200 OK if segments in the local cache have been loaded, and 503 SERVICE UNAVAILABLE, if they haven't.