---
title: "Api Cache Key Retrieve"
method: GET
path: "/api/cache/key/{cache_key}/"
tags: ["logs"]
---

# Api Cache Key Retrieve

`GET /api/cache/key/{cache_key}/`

GET/PATCH/DELETE /api/caches/<cache_key>/ — Retrieve, update, delete by cache_key.
GET/PATCH/DELETE /api/cache/<id>/ — Legacy alias, lookup by integer PK (JWT only).
GET/PATCH/DELETE /api/cache/key/<cache_key>/ — Legacy alias, lookup by cache_key.

JWT auth uses pk lookup when an integer id is supplied; otherwise (and for
API key auth) lookup is by cache_key_by_org_uuid.

## Path parameters

- `cache_key` string, required

## Headers

- `Authorization` string, required

## Response `200`

- PublicCachedResponseDetail — Strip org-internal fields and present a single cache_key for the public API. The PG ORM has two fields: - cache_key: internal key with integer org ID (legacy, used by CH enrichment) - cache_key_by_org_uuid: UUID-based key (safe to expose) The public API exposes ONE "cache_key" field whose value comes from cache_key_by_org_uuid. The internal cache_key and the raw cache_key_by_org_uuid field are both removed from the response.
  - `cache_key` string, nullable
  - `cache_key_by_org_uuid` string, nullable
  - `request_content` string, required
  - `prompt_content` string, required
  - `response_content` string, required
  - `prompt_messages` union
    - unknown
    - unknown
  - `full_response` unknown
  - `hit_count` integer
  - `response_time` number, double
  - `timestamp` string, date-time
  - `updated_at` string, date-time
  - `expiry_date` string, date-time, nullable

---

[API](https://skmtc.net/keywordsai/apis/api-reference.md) · [All operations](https://skmtc.net/keywordsai/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/keywordsai/api-reference/versions/c26d550029f8/schema)