---
title: "Create memory store API key"
method: POST
path: "/v1/memory-stores/{storeId}/api-keys"
tags: ["Agent Memory - Stores"]
---

# Create memory store API key

`POST /v1/memory-stores/{storeId}/api-keys`

## Request

- Base URL: `https://api.redislabs.com`
- URL: `https://api.redislabs.com/v1/memory-stores/{storeId}/api-keys`
- Auth: API key in header `x-api-key` and API key in header `x-api-secret-key` and API key in header `x-auth-token`

Create an API key for the Agent Memory store identified by store Id. The generated key value is returned once and cannot be retrieved again

## Path parameters

- `storeId` string, required

## Request body

- MemoryStoreApiKeyCreateRequest: Memory store API key creation request
  - `keyName` string, required: Name of the API key.

## Response `201`

API key created. The generated key value is returned once in the response body.

- MemoryStoreApiKeyCreateResponse: New memory store API key
  - `apiKey` string, password: Generated API key. Returned only once.

## Other responses

- `400`: Bad Request - The server cannot process the request due to something that is perceived to be a client error
- `401`: Unauthorized - Authentication failed for requested resource
- `403`: Forbidden - Not allowed to create requested resource (primarily due to not active resource)
- `404`: Not Found - The resource you were trying to reach was not found or does not exist
- `408`: Request Timeout - The server didn't receive a complete request message within the server's allotted timeout period
- `409`: Conflict - request could not be processed because of a conflict (primarily due to another resource that exist with the new name
- `412`: Precondition Failed - Feature flag for this flow is off
- `422`: Unprocessable Entity - The server understands the request, and the syntax of the request is correct, but it was unable to process the contained instructions
- `424`: Failed Dependency - The memory store's database is unavailable or out of memory, e.g. /errors/resource-unavailable or /errors/database-out-of-memory. When the error originates from the Agent Memory service the body is an application/problem+json document (MemoryProblemDetails) carrying the service's error type and detail
- `429`: Too Many Requests - Too many resources are concurrently created / updated / deleted in the account. Please re-submit API requests after resource changes are completed)
- `500`: Internal system error - If this error persists, please contact customer support
- `503`: Service Unavailable - Server is temporarily unable to handle the request, please try again later. If this error persists, please contact customer support

## Changes

- **2026-10-02** `6b256e1bb946`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/redis/apis/redis-cloud-api/changes/v1/memory-stores/:storeId/api-keys/post.md)

---

[API](https://skmtc.dev/redis/apis/redis-cloud-api.md) - [All operations](https://skmtc.dev/redis/apis/redis-cloud-api/llms.txt) - [OpenAPI document](https://skmtc.dev/redis/apis/redis-cloud-api/revisions/5c114f33e7d5?raw)