Query API key information API

Query API key information API

New API reference

For the most up-to-date API details, refer to Security APIs.

Retrieves information for API keys with Query DSL in a paginated fashion.

Request

GET /_security/_query/api_key

POST /_security/_query/api_key

Prerequisites

  • To use this API, you must have at least the manage_own_api_key or the read_security cluster privileges.
  • If you have only the manage_own_api_key privilege, this API returns only the API keys that you own. If you have the read_security, manage_api_key or greater privileges (including manage_security), this API returns all API keys regardless of ownership.

Description

Use this API to retrieve the API keys created with the create API key API in a paginated manner. You can optionally filter the results with a query.

Path parameters

with_limited_by

(Optional, Boolean) A boolean flag to return the snapshot of the owner user’s role descriptors associated with the API key. An API key’s actual permission is the intersection of its assigned role descriptors and the owner user’s role descriptors (effectively limited by it). An API key cannot retrieve any API key’s limited-by role descriptors (including itself) unless it has manage_api_key or higher privileges.

with_profile_uid

(Optional, boolean) Determines whether to also retrieve the user profile uid, for the API key owner user. If it exists, the profile uid is returned under the profile_uid response field for each API key. Defaults to false.

typed_keys

(Optional, Boolean) If true, aggregation names are prefixed by their respective types in the response. Defaults to false.

Request body

You can specify the following parameters in the request body:

query

(Optional, object) A query to filter which API keys to return. If the query parameter is missing, it is equivalent to a match_all query. The query supports a subset of query types, including match_all, bool, term, terms, match, ids, prefix, wildcard, exists, range, and simple query string.

You can query the following public values associated with an API key.

The queryable string values associated with API keys are internally mapped as keywords. Consequently, if no analyzer parameter is specified for a match query, then the provided match query string is interpreted as a single keyword value. Such a match query is hence equivalent to a term query.

Valid values for query

  • id

    ID of the API key. Note id must be queried with the ids query.

    type

    API keys can be of type rest, if created via the Create API key or the Grant API key APIs, or of type cross_cluster if created via the Create Cross-Cluster API key API.

    name

    Name of the API key.

    creation

    Creation time of the API key in milliseconds.

    expiration

    Expiration time of the API key in milliseconds. This is null if the key was not configured to expire.

    invalidated

    Indicates whether the API key is invalidated. If true, the key is invalidated. Defaults to false.

    invalidation

    Invalidation time of the API key in milliseconds. This field is only set for invalidated API keys.

    username

    Username of the API key owner.

    realm

    Realm name of the API key owner.

    metadata

    Metadata field associated with the API key, such as metadata.my_field. Metadata is internally indexed as a flattened field type. This means that all fields act like keyword fields when querying and sorting. It’s not possible to refer to a subset of metadata fields using wildcard patterns, e.g. metadata.field*, even for query types that support field name patterns. Lastly, all the metadata fields can be searched together when simply mentioning metadata (not followed by any dot and sub-field name).

You cannot query the role descriptors of an API key.

aggs or aggregations

(Optional, object) Any aggregations to run over the corpus of returned API keys. Aggregations and queries work together. Aggregations are computed only on the API keys that match the query. This supports only a subset of aggregation types, namely: terms, range, date range, missing, cardinality, value count, composite, filter, and filters. Additionally, aggregations only run over the same subset of fields that query works with.

from

(Optional, integer) Starting document offset. Needs to be non-negative and defaults to 0.

By default, you cannot page through more than 10,000 hits using the from and size parameters. To page through more hits, use the search_after parameter.

size

(Optional, integer) The number of hits to return. Must not be negative and defaults to 10. The size parameter can be set to 0, in which case no API key matches are returned, only the aggregation results.

By default, you cannot page through more than 10,000 hits using the from and size parameters. To page through more hits, use the search_after parameter.

sort

(Optional, object) Sort definition. Other than id, all public fields of an API key are eligible for sorting. In addition, sort can also be applied to the _doc field to sort by index order.

search_after

(Optional, array) Search after definition.

Response body

This API returns the following top level fields:

total

The total number of API keys found.

count

The number of API keys returned in the response.

api_keys

A list of API key information.

Examples

The following request lists all API keys, assuming you have the manage_api_key privilege:

  1. resp = client.security.query_api_keys()
  2. print(resp)
  1. const response = await client.security.queryApiKeys();
  2. console.log(response);
  1. GET /_security/_query/api_key

A successful call returns a JSON structure that contains the information retrieved from one or more API keys:

  1. {
  2.   "total": 3,
  3.   "count": 3,
  4.   "api_keys": [ 
  5.     {
  6.       "id": "nkvrGXsB8w290t56q3Rg",
  7.       "name": "my-api-key-1",
  8.       "creation": 1628227480421,
  9.       "expiration": 1629091480421,
  10.       "invalidated": false,
  11.       "username": "elastic",
  12.       "realm": "reserved",
  13.       "realm_type": "reserved",
  14.       "metadata": {
  15.         "letter": "a"
  16.       },
  17.       "role_descriptors": { 
  18.         "role-a": {
  19.           "cluster": [
  20.             "monitor"
  21.           ],
  22.           "indices": [
  23.             {
  24.               "names": [
  25.                 "index-a"
  26.               ],
  27.               "privileges": [
  28.                 "read"
  29.               ],
  30.               "allow_restricted_indices": false
  31.             }
  32.           ],
  33.           "applications": [ ],
  34.           "run_as": [ ],
  35.           "metadata": { },
  36.           "transient_metadata": {
  37.             "enabled": true
  38.           }
  39.         }
  40.       }
  41.     },
  42.     {
  43.       "id": "oEvrGXsB8w290t5683TI",
  44.       "name": "my-api-key-2",
  45.       "creation": 1628227498953,
  46.       "expiration": 1628313898953,
  47.       "invalidated": false,
  48.       "username": "elastic",
  49.       "realm": "reserved",
  50.       "metadata": {
  51.         "letter": "b"
  52.       },
  53.       "role_descriptors": { } 
  54.     }
  55.   ]
  56. }

The list of API keys that were retrieved for this request

The role descriptors that are assigned to this API key when it was created or last updated. Note the API key’s effective permissions are an intersection of its assigned privileges and the point-in-time snapshot of the owner user’s permissions.

An empty role descriptors means the API key inherits the owner user’s permissions.

If you create an API key with the following details:

  1. resp = client.security.create_api_key(
  2.     name="application-key-1",
  3.     metadata={
  4.         "application": "my-application"
  5.     },
  6. )
  7. print(resp)
  1. const response = await client.security.createApiKey({
  2.   name: "application-key-1",
  3.   metadata: {
  4.     application: "my-application",
  5.   },
  6. });
  7. console.log(response);
  1. POST /_security/api_key
  2. {
  3.   "name": "application-key-1",
  4.   "metadata": { "application": "my-application"}
  5. }

A successful call returns a JSON structure that provides API key information. For example:

  1. {
  2.   "id": "VuaCfGcBCdbkQm-e5aOx",
  3.   "name": "application-key-1",
  4.   "api_key": "ui2lp2axTNmsyakw9tvNnw",
  5.   "encoded": "VnVhQ2ZHY0JDZGJrUW0tZTVhT3g6dWkybHAyYXhUTm1zeWFrdzl0dk5udw=="
  6. }

Use the information from the response to retrieve the API key by ID:

  1. resp = client.security.query_api_keys(
  2.     with_limited_by=True,
  3.     query={
  4.         "ids": {
  5.             "values": [
  6.                 "VuaCfGcBCdbkQm-e5aOx"
  7.             ]
  8.         }
  9.     },
  10. )
  11. print(resp)
  1. const response = await client.security.queryApiKeys({
  2.   with_limited_by: "true",
  3.   query: {
  4.     ids: {
  5.       values: ["VuaCfGcBCdbkQm-e5aOx"],
  6.     },
  7.   },
  8. });
  9. console.log(response);
  1. GET /_security/_query/api_key?with_limited_by=true
  2. {
  3.   "query": {
  4.     "ids": {
  5.       "values": [
  6.         "VuaCfGcBCdbkQm-e5aOx"
  7.       ]
  8.     }
  9.   }
  10. }

A successful call returns a JSON structure for API key information including its limited-by role descriptors:

  1. {
  2.   "api_keys": [
  3.     {
  4.       "id": "VuaCfGcBCdbkQm-e5aOx",
  5.       "name": "application-key-1",
  6.       "creation": 1548550550158,
  7.       "expiration": 1548551550158,
  8.       "invalidated": false,
  9.       "username": "myuser",
  10.       "realm": "native1",
  11.       "realm_type": "native",
  12.       "metadata": {
  13.         "application": "my-application"
  14.       },
  15.       "role_descriptors": { },
  16.       "limited_by": [ 
  17.         {
  18.           "role-power-user": {
  19.             "cluster": [
  20.               "monitor"
  21.             ],
  22.             "indices": [
  23.               {
  24.                 "names": [
  25.                   "*"
  26.                 ],
  27.                 "privileges": [
  28.                   "read"
  29.                 ],
  30.                 "allow_restricted_indices": false
  31.               }
  32.             ],
  33.             "applications": [ ],
  34.             "run_as": [ ],
  35.             "metadata": { },
  36.             "transient_metadata": {
  37.               "enabled": true
  38.             }
  39.           }
  40.         }
  41.       ]
  42.     }
  43.   ]
  44. }

The owner user’s permissions associated with the API key. It is a point-in-time snapshot captured at creation and subsequent updates. An API key’s effective permissions are an intersection of its assigned privileges and the owner user’s permissions.

You can also retrieve the API key by name:

  1. resp = client.security.query_api_keys(
  2.     query={
  3.         "term": {
  4.             "name": {
  5.                 "value": "application-key-1"
  6.             }
  7.         }
  8.     },
  9. )
  10. print(resp)
  1. const response = await client.security.queryApiKeys({
  2.   query: {
  3.     term: {
  4.       name: {
  5.         value: "application-key-1",
  6.       },
  7.     },
  8.   },
  9. });
  10. console.log(response);
  1. GET /_security/_query/api_key
  2. {
  3.   "query": {
  4.     "term": {
  5.       "name": {
  6.         "value": "application-key-1"
  7.       }
  8.     }
  9.   }
  10. }

Use a bool query to issue complex logical conditions and use from, size, sort to help paginate the result:

  1. GET /_security/_query/api_key
  2. {
  3.   "query": {
  4.     "bool": {
  5.       "must": [
  6.         {
  7.           "prefix": {
  8.             "name": "app1-key-" 
  9.           }
  10.         },
  11.         {
  12.           "term": {
  13.             "invalidated": "false" 
  14.           }
  15.         }
  16.       ],
  17.       "must_not": [
  18.         {
  19.           "term": {
  20.             "name": "app1-key-01" 
  21.           }
  22.         }
  23.       ],
  24.       "filter": [
  25.         {
  26.           "wildcard": {
  27.             "username": "org-*-user" 
  28.           }
  29.         },
  30.         {
  31.           "term": {
  32.             "metadata.environment": "production" 
  33.           }
  34.         }
  35.       ]
  36.     }
  37.   },
  38.   "from": 20, 
  39.   "size": 10, 
  40.   "sort": [ 
  41.     { "creation": { "order": "desc", "format": "date_time" } },
  42.     "name"
  43.   ]
  44. }

The API key name must begin with app1-key-

The API key must still be valid

The API key name must not be app1-key-01

The API key must be owned by a username of the wildcard pattern org-*-user

The API key must have the metadata field environment that has the value of production

The offset to begin the search result is the 20th (zero-based index) API key

The page size of the response is 10 API keys

The result is first sorted by creation date in descending order, then by name in ascending order

The response contains a list of matched API keys along with their sort values:

  1. {
  2.   "total": 100,
  3.   "count": 10,
  4.   "api_keys": [
  5.     {
  6.       "id": "CLXgVnsBOGkf8IyjcXU7",
  7.       "name": "app1-key-79",
  8.       "creation": 1629250154811,
  9.       "invalidated": false,
  10.       "username": "org-admin-user",
  11.       "realm": "native1",
  12.       "metadata": {
  13.         "environment": "production"
  14.       },
  15.       "role_descriptors": { },
  16.       "_sort": [
  17.         "2021-08-18T01:29:14.811Z",  
  18.         "app1-key-79"  
  19.       ]
  20.     },
  21.     {
  22.       "id": "BrXgVnsBOGkf8IyjbXVB",
  23.       "name": "app1-key-78",
  24.       "creation": 1629250153794,
  25.       "invalidated": false,
  26.       "username": "org-admin-user",
  27.       "realm": "native1",
  28.       "metadata": {
  29.         "environment": "production"
  30.       },
  31.       "role_descriptors": { },
  32.       "_sort": [
  33.         "2021-08-18T01:29:13.794Z",
  34.         "app1-key-78"
  35.       ]
  36.     },
  37.     ...
  38.   ]
  39. }

The first sort value is creation time, which is displayed in date_time format as defined in the request

The second sort value is the API key name

Aggregations Example

For example, given 2 users “june” and “king”, each owning 3 API keys:

  • one that never expires (invalidated for user “king”)
  • one that expires in 10 days
  • and one that expires in 100 day (invalidated for user “june”)

the following request returns the names of valid (not expired and not invalidated) API keys that expire soon (in 30 days time), grouped by owner username.

Request

  1. resp = client.security.query_api_keys(
  2.     size=0,
  3.     query={
  4.         "bool": {
  5.             "must": {
  6.                 "term": {
  7.                     "invalidated": False
  8.                 }
  9.             },
  10.             "should": [
  11.                 {
  12.                     "range": {
  13.                         "expiration": {
  14.                             "gte": "now"
  15.                         }
  16.                     }
  17.                 },
  18.                 {
  19.                     "bool": {
  20.                         "must_not": {
  21.                             "exists": {
  22.                                 "field": "expiration"
  23.                             }
  24.                         }
  25.                     }
  26.                 }
  27.             ],
  28.             "minimum_should_match": 1
  29.         }
  30.     },
  31.     aggs={
  32.         "keys_by_username": {
  33.             "composite": {
  34.                 "sources": [
  35.                     {
  36.                         "usernames": {
  37.                             "terms": {
  38.                                 "field": "username"
  39.                             }
  40.                         }
  41.                     }
  42.                 ]
  43.             },
  44.             "aggs": {
  45.                 "expires_soon": {
  46.                     "filter": {
  47.                         "range": {
  48.                             "expiration": {
  49.                                 "lte": "now+30d/d"
  50.                             }
  51.                         }
  52.                     },
  53.                     "aggs": {
  54.                         "key_names": {
  55.                             "terms": {
  56.                                 "field": "name"
  57.                             }
  58.                         }
  59.                     }
  60.                 }
  61.             }
  62.         }
  63.     },
  64. )
  65. print(resp)
  1. const response = await client.security.queryApiKeys({
  2.   size: 0,
  3.   query: {
  4.     bool: {
  5.       must: {
  6.         term: {
  7.           invalidated: false,
  8.         },
  9.       },
  10.       should: [
  11.         {
  12.           range: {
  13.             expiration: {
  14.               gte: "now",
  15.             },
  16.           },
  17.         },
  18.         {
  19.           bool: {
  20.             must_not: {
  21.               exists: {
  22.                 field: "expiration",
  23.               },
  24.             },
  25.           },
  26.         },
  27.       ],
  28.       minimum_should_match: 1,
  29.     },
  30.   },
  31.   aggs: {
  32.     keys_by_username: {
  33.       composite: {
  34.         sources: [
  35.           {
  36.             usernames: {
  37.               terms: {
  38.                 field: "username",
  39.               },
  40.             },
  41.           },
  42.         ],
  43.       },
  44.       aggs: {
  45.         expires_soon: {
  46.           filter: {
  47.             range: {
  48.               expiration: {
  49.                 lte: "now+30d/d",
  50.               },
  51.             },
  52.           },
  53.           aggs: {
  54.             key_names: {
  55.               terms: {
  56.                 field: "name",
  57.               },
  58.             },
  59.           },
  60.         },
  61.       },
  62.     },
  63.   },
  64. });
  65. console.log(response);
  1. POST /_security/_query/api_key
  2. {
  3.   "size": 0,
  4.   "query": {
  5.     "bool": {
  6.       "must": {
  7.         "term": {
  8.           "invalidated": false  
  9.         }
  10.       },
  11.       "should": [  
  12.         {
  13.           "range": { "expiration": { "gte": "now" } }
  14.         },
  15.         {
  16.           "bool": { "must_not": { "exists": { "field": "expiration" } } }
  17.         }
  18.       ],
  19.       "minimum_should_match": 1
  20.     }
  21.   },
  22.   "aggs": {
  23.     "keys_by_username": {
  24.       "composite": {
  25.         "sources": [ { "usernames": { "terms": { "field": "username" } } } ]  
  26.       },
  27.       "aggs": {
  28.         "expires_soon": {
  29.           "filter": {
  30.             "range": { "expiration": { "lte": "now+30d/d" } }  
  31.           },
  32.           "aggs": {
  33.             "key_names": { "terms": { "field": "name" } }
  34.           }
  35.         }
  36.       }
  37.     }
  38.   }
  39. }

Matching API keys must not be invalidated

Matching API keys must be either not expired or not have an expiration date

Aggregate all matching keys (i.e. all valid keys) by their owner username

Further aggregate the per-username valid keys into a soon-to-expire bucket

Response

  1. {
  2.   "total" : 4,  
  3.   "count" : 0,
  4.   "api_keys" : [ ],
  5.   "aggregations" : {
  6.     "keys_by_username" : {
  7.       "after_key" : {
  8.         "usernames" : "king"
  9.       },
  10.       "buckets" : [
  11.         {
  12.           "key" : {
  13.             "usernames" : "june"
  14.           },
  15.           "doc_count" : 2,  
  16.           "expires_soon" : {
  17.             "doc_count" : 1,
  18.             "key_names" : {
  19.               "doc_count_error_upper_bound" : 0,
  20.               "sum_other_doc_count" : 0,
  21.               "buckets" : [
  22.                 {
  23.                   "key" : "june-key-10",
  24.                   "doc_count" : 1
  25.                 }
  26.               ]
  27.             }
  28.           }
  29.         },
  30.         {
  31.           "key" : {
  32.             "usernames" : "king"
  33.           },
  34.           "doc_count" : 2,
  35.           "expires_soon" : {
  36.             "doc_count" : 1,  
  37.             "key_names" : {
  38.               "doc_count_error_upper_bound" : 0,
  39.               "sum_other_doc_count" : 0,
  40.               "buckets" : [  
  41.                 {
  42.                   "key" : "king-key-10",
  43.                   "doc_count" : 1
  44.                 }
  45.               ]
  46.             }
  47.           }
  48.         }
  49.       ]
  50.     }
  51.   }
  52. }

Total number of valid API keys (2 for each user)

Number of valid API keys for user “june”

Number of valid API keys expiring soon for user “king”

The names of soon-to-expire API keys for user “king”

To retrieve the invalidated (but not yet deleted) API keys, grouped by owner username and API key name, issue the following request:

Request

  1. resp = client.security.query_api_keys(
  2.     size=0,
  3.     query={
  4.         "bool": {
  5.             "filter": {
  6.                 "term": {
  7.                     "invalidated": True
  8.                 }
  9.             }
  10.         }
  11.     },
  12.     aggs={
  13.         "invalidated_keys": {
  14.             "composite": {
  15.                 "sources": [
  16.                     {
  17.                         "username": {
  18.                             "terms": {
  19.                                 "field": "username"
  20.                             }
  21.                         }
  22.                     },
  23.                     {
  24.                         "key_name": {
  25.                             "terms": {
  26.                                 "field": "name"
  27.                             }
  28.                         }
  29.                     }
  30.                 ]
  31.             }
  32.         }
  33.     },
  34. )
  35. print(resp)
  1. const response = await client.security.queryApiKeys({
  2.   size: 0,
  3.   query: {
  4.     bool: {
  5.       filter: {
  6.         term: {
  7.           invalidated: true,
  8.         },
  9.       },
  10.     },
  11.   },
  12.   aggs: {
  13.     invalidated_keys: {
  14.       composite: {
  15.         sources: [
  16.           {
  17.             username: {
  18.               terms: {
  19.                 field: "username",
  20.               },
  21.             },
  22.           },
  23.           {
  24.             key_name: {
  25.               terms: {
  26.                 field: "name",
  27.               },
  28.             },
  29.           },
  30.         ],
  31.       },
  32.     },
  33.   },
  34. });
  35. console.log(response);
  1. POST /_security/_query/api_key
  2. {
  3.   "size": 0,
  4.   "query": {
  5.     "bool": {
  6.       "filter": {
  7.         "term": {
  8.           "invalidated": true
  9.         }
  10.       }
  11.     }
  12.   },
  13.   "aggs": {
  14.     "invalidated_keys": {
  15.       "composite": {
  16.         "sources": [
  17.           { "username": { "terms": { "field": "username" } } },
  18.           { "key_name": { "terms": { "field": "name" } } }
  19.         ]
  20.       }
  21.     }
  22.   }
  23. }

Response

  1. {
  2.   "total" : 2,
  3.   "count" : 0,
  4.   "api_keys" : [ ],
  5.   "aggregations" : {
  6.     "invalidated_keys" : {
  7.       "after_key" : {
  8.         "username" : "king",
  9.         "key_name" : "king-key-no-expire"
  10.       },
  11.       "buckets" : [
  12.         {
  13.           "key" : {
  14.             "username" : "june",
  15.             "key_name" : "june-key-100"
  16.           },
  17.           "doc_count" : 1
  18.         },
  19.         {
  20.           "key" : {
  21.             "username" : "king",
  22.             "key_name" : "king-key-no-expire"
  23.           },
  24.           "doc_count" : 1
  25.         }
  26.       ]
  27.     }
  28.   }
  29. }