After you create a redirect, you want to confirm it is actually firing — and see which redirects carry the traffic.
redirects/list-hit-log returns the redirect hit log: requests that matched a redirect and were sent on, each with the source URL, the target, the time and the user agent.
At a glance
| Ability | redirects/list-hit-log |
| Toolset | Redirection — toolset/redirection |
| Group | Redirection |
| Requires | Redirection, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.43 and later |
How it works
Page through recent hits, newest first. Each row records a request that matched a redirect and was sent on.
Logging has to be enabled in Redirection’s settings for rows to appear — check with Get Redirection Settings.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
per_page | integer | No | Page size, 5–200 (default 25). |
page | integer | No | 1-based page number. |
What comes back
| Name | Type | What it is |
|---|---|---|
hits | array | Recent redirect hits with source, target, time and agent. |
count | integer | How many were returned on this page. |
total | integer | How many are logged in total. |
page | integer | The page returned. |
success | boolean | Whether the call completed. |
Example
Ask your assistant:
Show me recent redirect hits.
It resolves to one call:
{
"ability": "redirects/list-hit-log",
"parameters": {
"per_page": 25
}
}Worth knowing
- Read-only — it reads the hit log and writes nothing.
- Logging must be enabled in Redirection’s settings for hits to be recorded.
- Needs the Redirection plugin active; without it you get a clear “not active” message.
Related abilities
- Get Redirection Settings — check whether logging is on
- List Redirects — see the redirects that fire
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category