# Data access log

The workspace **Data access log** records every request that an API key or a connected app made to read the data of the workspace. Use it to see who read your data, when, and what they read.

## Before you start [#before-you-start]

- To open the page, go to the workspace **Settings** and click **Data access log** in the **Workspace Settings** sidebar.
- Every role can open the page. Owners and admins see every request. A member sees only the requests from the API keys and connected apps that they created.
- The log shows API and MCP requests only. It does not show what people do in the app.

## Requests card [#requests-card]

Owners and admins see the **Requests** card. A member sees the same card as **Your activity**.

The card groups requests that one credential made close together into one row. A credential is an API key or a connected app. Each row shows:

- The time of the first request.
- The name of the credential, or **Deleted credential**.
- A chip: **API key** or **Connected app**.
- A summary, for example "6 requests · 15 credits", or **Free**.
- A red chip such as **2 failed**, if some requests failed.

Hover over the credential name to see **Owned by**, **What it did** and **Credential**.

### Request details [#request-details]

Click a row to open it. The list shows each request with its time, the endpoint in plain words and its credits. A failed request shows its status code.

**Owned by** names the member who created the credential. It does not name the person who sent the request, because anybody who has an API key can use it.

A request costs 0 credits when VitalSentinel answered from its cache, when the endpoint is free, or when it failed. VitalSentinel never charges a request that did not succeed.

### Failed requests [#failed-requests]

If some requests on the page failed or were refused, the card shows a warning such as **3 failed or refused on this page**.

## Date range [#date-range]

The filter bar at the bottom of the page sets the date range. The options are the last 7, 28, 30 and 90 days, and **This cycle** (the current billing cycle). The default is the last 28 days.

If no request was made in the range, the page shows **No API access in this period**.

## Download the log as CSV [#download-the-log-as-csv]

1. Select the date range in the filter bar.
2. Click **Download CSV**.

The message **Data access log downloaded** confirms it. The button is not available when the log has no rows. If you are a member, the file contains only the requests from your own API keys and connected apps.

## Troubleshooting [#troubleshooting]

### Why is the Data access log empty? [#why-is-the-data-access-log-empty]

If nobody used an API key or connected app in the date range, the page shows **No API access in this period**. Select a longer date range. If you are a member, you see only your own credentials.

### What is the difference between the Data access log and the API credits page? [#what-is-the-difference-between-the-data-access-log-and-the-api-credits-page]

The [API credits](/workspace/api-credits) page shows the credits billed to this workspace in the current cycle. The **Data access log** shows every request that read this workspace's data, with a longer date range and a CSV export.

### Who sent a request with an API key? [#who-sent-a-request-with-an-api-key]

The log shows who created the key (**Owned by**), not who used it. If you do not know a key, revoke it on the [API access](/account/api-access) page.

## Related [#related]

- [API credits](/workspace/api-credits) - the credit balance and spending log
- [API access](/account/api-access) - create and revoke API keys
- [Connected apps](/account/connected-apps) - revoke apps you no longer use
- [API introduction](/api/introduction) - get started with the API