> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs-beta.getzep.com/v3/api-logging/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs-beta.getzep.com/_mcp/server. # API logging > **Info** > > Available to [Flex Plus and Enterprise](https://www.getzep.com/pricing) customers. API Logs record supported request information for SDK and API activity that uses project API keys. Use these logs to monitor usage, debug integrations, and support query-audit workflows. > **Note** > > API logs track requests made with project API keys. Webapp requests are not included. For webapp activity, see [Audit logging](/audit-logging). ## What is logged An API log entry can include: | Field | Description | | ------------ | ------------------------------------------ | | **Time** | When the request was made | | **Method** | HTTP method (GET, POST, PUT, DELETE) | | **Endpoint** | The API endpoint called | | **Status** | HTTP status code (2xx, 4xx, 5xx) | | **Latency** | Response time in milliseconds | | **API Key** | Which API key was used (name + masked key) | ## Viewing API logs Access API logs from your account settings: 1. Navigate to **Account Settings** in the Zep dashboard 2. Select **API Logs** from the sidebar 3. Browse the chronological list of requests Results are sorted by most recent first. ## Query audit Use the endpoint, time, API key, status, and request correlation information that is available in API Logs to review graph-search and context-retrieval activity. API Logs show the recorded API request. They do not reconstruct an arbitrary generated answer. To audit an answer to its source data, your application must retain the retrieval results and the source episode references that it used for that answer. ## Access control Viewing API logs requires the **API Logs View** permission. Configure this through [managing team access](/role-based-access-control). > Review recorded SDK and API request activity