search docs
Edit on GitHub

Key-value store

Documentation of Key-value stores, which allow you to store any kind of data, e.g. JSON documents or images.

The key-value store is simple storage that can be used for storing any kind of data. It can be JSON or HTML documents, zip files, images, or simply strings. The data are stored along with their MIME content type.

Each actor run is assigned its own key-value store when it is created. The store contains the actor's input, and, if necessary, other stores such as its output.

Key-value stores are mutable–you can both add entries and delete them.

Named key-value stores are retained indefinitely.
Unnamed key-value stores expire after 7 days unless otherwise specified.
Learn about named and unnamed key-value stores.

Basic usage

There are four ways to access your key-value stores:

Apify app

In the Apify app, you can view your key-value stores in the Storage section under the Key-value stores tab.

Only named key-value stores are displayed by default. Select the Include unnamed key-value stores checkbox to display all of your stores.

Key-value stores in app

To view a key-value store's content, click on its Store ID, then click on a store's View button. In the detail page, under the Settings tab, you can update the store's name (and, in turn, its retention period) and access rights. The API tab allows you to view and test a store's API endpoints.

Key-value stores detail

Apify SDK

If you are building an Apify actor, you will be using the Apify software development kit (SDK). In the Apify SDK, the key-value store is represented by the KeyValueStore class.

You can use the KeyValueStore class to specify whether your data is stored locally or in the Apify cloud, get and set values using the Apify.getValue() and Apify.setValue() methods or iterate over your key-value store keys using the forEachKey() method.

Each actor run is associated with the default key-value store, which is created for the actor run. When running your actors and storing data locally, you can pass its input using the INPUT.json key-value store.

You can find INPUT.json and other key-value stores in the location below.


The default key-value store's ID is default. The {KEY} is the record's key and {EXT} corresponds to the data value's MIME content type.

To manage your key-value stores, you can use the following methods. For a full list of methods, see the KeyValueStore class's API reference.

// Get the default input
const input = await Apify.getInput();

// Open a named key-value store
const exampleStore = await Apify.openKeyValueStore("my-store");

// Read a record in the `exampleStore` storage
const value = await exampleStore.getValue("some-key");

// Write a record to `exampleStore`
await exampleStore.setValue("some-key", { foo: "bar" });

// Delete a record in `exampleStore`
await exampleStore.setValue("some-key", null);

Note that JSON is automatically parsed to a JavaScript object, text data returned as a string and other data is returned as binary buffer.

const Apify = require("apify");

// The optional Apify.main() function performs the
// actor's job and terminates the process when it is finished
Apify.main(async () => {
    // Get input of your actor
    const input = await Apify.getInput();
    const value = await Apify.getValue("my-key");


    await Apify.setValue(
        { contentType: "image/jpeg" }

The Apify.getInput()method is not only a shortcut to Apify.getValue("INPUT")- it is also compatible with Apify.metamorph() [docs]. This is because a metamorphed actor run's input is stored in the INPUT-METAMORPH-1 key instead of INPUT, which hosts the original input.

For more information on managing your key-value stores with the Apify SDK, see the SDK documentation and the KeyValueStore class's API reference.

JavaScript API client

Apify's JavaScript API client (apify-client) allows you to access your key-value stores from any Node.js application, whether it is running on the Apify platform or elsewhere.

For help with setting up the client, see the JavaScript API client section on the overview page.

After importing the apify-client package into your application and creating an instance of it, save it to a variable for easier access.

// Save your key-value stores to a variable for easier access
const keyValueStores = apifyClient.keyValueStores;

You can then access your stores, retrieve records in stores, write new records or delete records.

// Get the `my-store` key-value store or create it
// if it doesn't exist and set it as the default
const exampleStore = await keyValueStores.getOrCreateStore({
    storeName: "my-store"
apifyClient.setOptions({ storeId: });

// Get a record from `exampleStore` 
const record = await keyValueStores.getRecord({ key: "foo" });

// Write a record to the `exampleStore` storage
await keyValueStores.putRecord({
    key: "foo",
    body: "bar",
    contentType: "text/plain; charset=utf-8",

// Delete a record in `exampleStore`
await keyValueStores.deleteRecord({ key: "foo" });

For more information on managing your key-value stores using the JavaScript API client, see its documentation.

Apify API

The Apify API allows you to access your key-value stores programmatically using HTTP requests and easily share your crawling results.

If you are accessing your stores using the username~store-name store ID format, you will need to append your secret API token as a query parameter (see below). You can find the token (and your user ID) on the Integrations page of your Apify account.

To get a list of your key-value stores, send a GET request to the Get list of key-value stores endpoint, providing your secret API token as a query parameter.{YOUR_API_TOKEN}

To get information about a key-value store such as its creation time and item count, send a GET request to the Get store endpoint.{STORE_ID}?token={YOUR_API_TOKEN}

To get a record (its value) from a key-value store, send a GET request to the Get record endpoint.{STORE_ID}/records/{KEY_ID}?token={YOUR_API_TOKEN}

To add a record to a specific key in a key-value store, send a PUT request to the Put record endpoint.{STORE_ID}/records/{KEY_ID}?token={YOUR_API_TOKEN}

Example payload:

    "foo": "bar",
    "fos": "baz"

When adding a record, the request payload is limited to 9MB. To upload a larger record or speed up your upload, use the Direct upload URL endpoint.

To delete a record, send a DELETE request specifying the key from a key-value store to the Delete record endpoint.{STORE_ID}/records/{KEY_ID}?token={YOUR_API_TOKEN}

For a detailed breakdown of each API endpoint, see the API documentation.

Sharing key-value stores between runs

You can access a key-value store from any actor or task run as long as you know its name or ID.

To access a key-value store from another run using the Apify SDK, open it using the Apify.openDataset([store]) method like you would any other store.

const otherStore = await Apify.openKeyValueStore("old-store");

To access a key-value store using the JavaScript API client, use the getOrCreateStore() method.

const otherStore = await keyValueStores.getOrCreateStore({
    storeName: "my-store",

Once you've opened a store, read and manage its contents like you would with a key-value store from your current run.

The same applies for the Apify API - you can use the same endpoints as you would normally.

For more information on sharing storages between runs, see the Storage overview page.

Data consistency

Key-value storage uses the AWS S3 service. According to the S3 documentation, it provides read-after-write consistency for newly-created items. This means that if a record does not exist and you create it, then read it right after, you will be able to see it.

However, S3 storage has a caveat, described in the below quote from the S3 documentation.

[...] if you make a HEAD or GET request to a key name before the object is created, then create the object shortly after that, a subsequent GET might not return the object due to eventual consistency.
Amazon S3 offers eventual consistency for overwrite PUTS and DELETES in all Regions.

Eventual consistency means that if you update a value and then retrieve it from storage, the value will be consistent with the last update eventually. Before enough time has passed, however, the returned value may be inconsistent.

Visit this article for more details on the issue and this article for some ideas on how to tackle the issue.


When adding a record using the Put record API endpoint, the request payload is limited to 9MB. To upload a larger record or speed up your upload, use the Direct upload URL endpoint.