---
title: "List my own action-log entries"
type: reference
method: GET
path: /rest-api/action-log/mine.do
tag: "Users"
---

# List my own action-log entries

`GET https://YOUR-NETWORK-DOMAIN/rest-api/action-log/mine.do`

The caller's own action-log entries, newest first: every operation this user ran in the console, over the REST API or through the AI assistant (MCP), reads included. Never another user's entries, whatever the role. Each entry carries at (ISO-8601 instant), via (UI, REST_API, LEGACY_REST, MCP, AI_CHAT or SYSTEM), action (the operation's log name), pathIds (the ids in the operation's path, comma-separated, or null) and details (what the entry logged - the arguments and, for a change made through MCP or the REST API, before: the values it replaced; values under a name that carries a secret, such as a password, hash, API key or token, are masked as ***). Page through them with start: entries are read by position in the log, so ones logged in the same second never fall between pages. Any logged-in user may read their own entries.

## Query params

| Name | Type | Required | Example | Description |
|---|---|---|---|---|
| `from` | string | no | `2026-10-05T08:00:00Z` | Only entries logged at or after this moment, ISO-8601 (e.g. 2026-10-05T08:00:00Z). Default: 24 hours ago |
| `start` | integer | no | `0` | Skip this many entries (zero-based position in the newest-first list). Default 0 |
| `limit` | integer | no | `100` | How many entries to return, 1-1000. Default 100 |

## Responses

- `200` — {success, entries:[{at, via, action, pathIds, details}], returned, more}
- `400` — limit outside 1-1000 or start below 0
- `401` — Authentication error
- `403` — Forbidden — insufficient permissions

## Example request

```bash
curl --request GET \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/action-log/mine.do?from=2026-10-05T08%3A00%3A00Z&start=0&limit=100' \
  --header 'X-Api-Key: YOUR_API_KEY'
```

Source: https://epom.com/ad-server/docs/api/users/get-action-log-mine