GET · Logs & monitoring
Read the tail of one log
Read the tail of one log
/api/v1/logs
Description
Returns {target, kind, source, path, lines[], lineCount, truncated}. truncated means the tail was capped at the requested lines (500 max), not that anything was lost. kind=email needs an email address as input; the other kinds take a domain.
Query parameters
| Name | Type | Description |
|---|---|---|
input
required
|
string |
A domain, email address, website URL, or Inleed service id — for example example.se, [email protected] or 42976. Resolved to the owning account automatically, and the resolved target is echoed back in the response.
|
kind
required
|
enum |
Which log: error (website errors), access (web requests), or email (mail logs — needs an email address as input). One of error, access, email.
|
contains
|
string | Only return lines containing this substring (case-insensitive). Use it to find one request or error without pulling the whole log. |
lines
|
integer | How many of the most recent lines to return. Default 50, maximum 500. Range 1–500. |
Responses
The specification does not describe this response body; the note in the rail says what to expect.
Every non-2xx response is an RFC 7807 problem with a stable
code.
Commonly returned errors
The codes this operation reaches on its own path: the auth stack, its own validation and
ownership checks, and the transport. Not a closed set — a shared code from the
full registry can still surface. Each links to the code’s own page,
the same URL its type dereferences to.