KV Store Endpoints

The /kv endpoints access Consul's simple key/value store, useful for storing service configuration or other metadata.

It is important to note that each datacenter has its own KV store, and there is no built-in replication between datacenters. If you are interested in replication between datacenters, please view the Consul Replicate project.

In order to perform atomic operations on multiple KV pairs (up to a limit of 64) please consider using transactions instead.

Read Key

This endpoint returns the specified key. If no key exists at the given path, a 404 is returned instead of a 200 response.

For multi-key reads (up to a limit of 64 KV operations) please consider using transactions instead.

If the recurse or keys query parameters are true, this endpoint will return an array of keys. In this case, the HTTP response includes the X-Consul-Results-Filtered-By-ACLs: true header if the response array excludes results due to ACL policy configuration. Refer to the HTTP API documentation for more information.

The table below shows this endpoint's support for blocking queries, consistency modes, agent caching, and required ACLs.

The corresponding CLI command is consul kv get.

Path Parameters

• key (string: "") - Specifies the path of the key to read.

Query Parameters

• dc (string: "") - Specifies the datacenter to query. This will default to the datacenter of the agent being queried.

• recurse (bool: false) - Specifies if the lookup should be recursive and treat key as a prefix instead of a literal match.

• raw (bool: false) - Specifies the response is just the raw value of the key, without any encoding or metadata.

• keys (bool: false) - Specifies to return only keys (no values or metadata). Specifying this parameter implies recurse.

• separator (string: "") - Specifies the string to use as a separator for recursive key lookups. This option is only used when paired with the keys parameter to limit the prefix of keys returned, only up to the given separator.

• ns (string: "") EnterpriseEnterprise - Specifies the namespace to query. You can also specify the namespace through other methods.

  For recursive lookups, the namespace may be specified as '*' to return results for all namespaces.

Sample Request

$ curl \
    http://127.0.0.1:8500/v1/kv/my-key

Sample Response

Metadata Response

[
  {
    "CreateIndex": 100,
    "ModifyIndex": 200,
    "LockIndex": 200,
    "Key": "zip",
    "Flags": 0,
    "Value": "dGVzdA==",
    "Session": "adf4238a-882b-9ddc-4a9d-5b6758e4159e"
  }
]

• CreateIndex is the internal index value that represents when the entry was created.

• ModifyIndex is the last index that modified this key. This index corresponds to the X-Consul-Index header value that is returned in responses, and it can be used to establish blocking queries by setting the ?index query parameter. You can even perform blocking queries against entire subtrees of the KV store: if ?recurse is provided, the returned X-Consul-Index corresponds to the latest ModifyIndex within the prefix, and a blocking query using that ?index will wait until any key within that prefix is updated.

• LockIndex is the number of times this key has successfully been acquired in a lock. If the lock is held, the Session key provides the session that owns the lock.

• Key is simply the full path of the entry.

• Flags is an opaque unsigned integer that can be attached to each entry. API consumers can use this field any way they choose for their application.

• Value is a base64-encoded blob of data.

Keys Response

When using the ?keys query parameter, the response structure changes to an array of strings instead of an array of JSON objects. Listing /web/ with a / separator may return:

["/web/bar", "/web/foo", "/web/subdir/"]

Using the key listing method may be suitable when you do not need the values or flags or want to implement a key-space explorer.

Raw Response

When using the ?raw endpoint, the response is not application/json, but is instead text/plain.

)k������z^�-�ɑj�q����#u�-R�r��T�D��٬�Y��l,�ιK��Fm��}�#e��

(Yes, that is intentionally a bunch of gibberish characters to showcase the response)

Create/Update Key

This endpoint updates the value of the specified key. If no key exists at the given path, the key will be created.

Even though the return type is application/json, the value is either true or false, indicating whether the create/update succeeded.

The table below shows this endpoint's support for blocking queries, consistency modes, agent caching, and required ACLs.

The corresponding CLI command is consul kv put.

Path Parameters

• key (string: "") - Specifies the path of the key.

Query Parameters

• dc (string: "") - Specifies the datacenter to query. This will default to the datacenter of the agent being queried.

• flags (int: 0) - Specifies an unsigned value between 0 and (2^64)-1 to store with the key. API consumers can use this field any way they choose for their application.

• cas (int: 0) - Specifies to use a Check-And-Set operation. This is very useful as a building block for more complex synchronization primitives. If the index is 0, Consul will only put the key if it does not already exist. If the index is non-zero, the key is only set if the index matches the ModifyIndex of that key.

• acquire (string: "") - Supply a session ID to use in a lock acquisition operation. This is useful as it allows leader election to be built on top of Consul. If the lock is not held and the session is valid, this increments the LockIndex and sets the Session value of the key in addition to updating the key contents. A key does not need to exist to be acquired. If the lock is already held by the given session, then the LockIndex is not incremented but the key contents are updated. This lets the current lock holder update the key contents without having to give up the lock and reacquire it. Note that an update that does not include the acquire parameter will proceed normally even if another session has locked the key.

  For an example of how to use the lock feature, check the Leader Election tutorial.

• release (string: "") - Supply a session ID to use in a release operation. This is useful when paired with ?acquire= as it allows clients to yield a lock. This will leave the LockIndex unmodified but will clear the associated Session of the key. The key must be held by this session to be unlocked.

• ns (string: "") EnterpriseEnterprise - Specifies the namespace to query. You can also specify the namespace through other methods.

Sample Payload

The payload is arbitrary, and is loaded directly into Consul as supplied.

Sample Requests

$ curl \
    --request PUT \
    --data @contents \
    http://127.0.0.1:8500/v1/kv/my-key

# or

$ curl \
    --request PUT \
    --data-binary @contents \
    http://127.0.0.1:8500/v1/kv/my-key

Sample Response

true

Delete Key

This endpoint deletes a single key or all keys sharing a prefix.

The table below shows this endpoint's support for blocking queries, consistency modes, agent caching, and required ACLs.

The corresponding CLI command is consul kv delete.

Path Parameters

• key (string: "") - Specifies the path of the key to delete.

Query Parameters

• dc (string: "") - Specifies the datacenter to query. This will default to the datacenter of the agent being queried. If the DC is invalid, the error "No path to datacenter" is returned.

• recurse (bool: false) - Specifies to delete all keys which have the specified prefix. Without this, only a key with an exact match will be deleted.

• cas (int: 0) - Specifies to use a Check-And-Set operation. This is very useful as a building block for more complex synchronization primitives. Unlike PUT, the index must be greater than 0 for Consul to take any action: a 0 index will not delete the key. If the index is non-zero, the key is only deleted if the index matches the ModifyIndex of that key.

• ns (string: "") EnterpriseEnterprise - Specifies the namespace to query. You can also specify the namespace through other methods.

Sample Request

$ curl \
    --request DELETE \
    http://127.0.0.1:8500/v1/kv/my-key

Sample Response

true

Methods to Specify Namespace EnterpriseEnterprise

The key-value store endpoints support several methods for specifying the namespace of resources with the following order of precedence:

1. ns query parameter
2. X-Consul-Namespace request header
3. Namespace is inherited from the namespace of the request's ACL token (if any)
4. The default namespace