Fetch User Grant History
Reputation Grant Endpoints
Fetch User Grant History
A single user’s full grant history, negative grants included — the only surface that exposes them
Fetch User Grant History
Returns one user’s complete reputation-grant history, received and sent, including negative grants. This is the only route on which negatives are readable: the public list endpoint bakes
A service key is presented as the bearer credential alongside
Both counterparties are hydrated with a display-only projection —
A
Rate limit: 25 requests per 5 minutes per IP. Exceeding it returns
amount > 0 into its query for every caller, so a service key sees no more there than an ordinary user does.
This is a dashboard route, not a /v7/:projectId route — it powers the grant-history dialog on a user’s detail view in the dashboard — but it is callable with a service or master key, which is how a backend reads its own moderation deductions back.
The route cannot issue grants. It is read-only.
Authentication and headers
string
The project UUID. Required when you authenticate with a service key — that header is how the server finds the project whose key you are presenting, and without it a raw project key is parsed as a dashboard session token and rejected with
403. Master keys and dashboard sessions only need the project named somewhere on the request, and may send it as a ?projectId= query parameter instead; supplying both is fine as long as they match.string
Set to
true when authenticating with a master key. Master keys are only recognized on requests carrying this header.x-sublay-project-id. Dashboard sessions authenticate with their client JWT as usual, naming the project in the header or the query string.
Requires the reputation bundle.
Path Parameters
string
required
UUID of the user whose history to read.
Query Parameters
string
"received" (grants credited to this user), "sent" (grants they issued), or "all" (either side). Defaults to "all".number
Page number (1-indexed). Defaults to
1.number
Results per page. Defaults to
20; the maximum is 100. A larger value is rejected with 400 user/invalid-query, not silently clamped.Response
Returns200 with the dashboard list shape. grants is always an array, never undefined, and is ordered newest first.
id, name, username, avatar. No sensitive user columns are returned. See ReputationGrant for the row shape.
Error Responses
Invalid Params — 400
Invalid Params — 400
Invalid Query — 400
Invalid Query — 400
limit above 100, a non-positive page, or a direction outside received / sent / all. The field path prefixes the message, so error reads "<path>: <message>".Tables Not Available — 403
Tables Not Available — 403
429 with a plain-text message and no code.
See also: ReputationGrant · Fetch Many Reputation Grants
