The visits endpoint exposes the raw, unprocessed log of every request that arrived at a linq domain. Each record corresponds to one individual request and includes the platform, browser, OS, referer, user agent, destination chosen, and forwarded query — but never the visitor’s IP address. For aggregated totals, charts, or ranked breakdowns, use the Analytics API instead; the visits endpoint is most useful for building custom exports, debugging redirect rules, or auditing traffic at the individual event level.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/org-quicko/linq/llms.txt
Use this file to discover all available pages before exploring further.
Client IP addresses are never stored in the visit log at any point in the processing pipeline. Platform, OS, and browser fields are derived solely from the
User-Agent request header.GET /api/v1/visits
Returns a paginated, newest-first list of visit records matching the supplied filters.Query Parameters
Restrict results to visits on a specific link. Pass
link_id of a known link to scope your query. Omit to see visits across all links (subject to other filters).Restrict results to visits on a specific domain.
When
"true", restricts the response to orphan visits — requests that matched no active link (unknown slug, archived link, or root path). Defaults to "false", which returns all visits regardless of link resolution.Return only visits that occurred at or after this instant. Accepts full ISO 8601 datetimes (e.g.
2024-05-01T00:00:00Z). Inclusive.Return only visits that occurred at or before this instant. Requires a full ISO 8601 datetime string including the
T separator (e.g. 2024-05-31T23:59:59Z). Inclusive.Filter by bot classification. One of:
"true"— return only bot visits"false"— return only human visits"any"— return all visits (default)
Filter to a specific platform. One of
android, ios, or desktop.Filter to visits from a specific OS (e.g.
windows, macos, linux). Exact match; the value is lowercased at the API boundary to match how it is stored. Open vocabulary — not a closed enum.Filter to visits from a specific browser (e.g.
chrome, safari, firefox). Exact match; the value is lowercased at the API boundary to match how it is stored. Open vocabulary — not a closed enum.Maximum number of records per page. Must be between 1 and 200.
Zero-based offset for pagination. Use with
limit to walk through the full result set.Response Envelope
The response is a standard list envelope:Array of visit objects for the current page.
Total number of visits matching the query (across all pages).
The effective page size used for this request.
The offset used for this request.
Example
- Human visits on a link
- Date-bounded with platform filter
- Response
Visit Object Fields
UUID (v7) uniquely identifying this visit record.
The UUID of the link this visit resolved to.
null for orphan visits — requests that matched no active link.The UUID of the domain that received this request.
The exact slug portion of the URL that was requested. For orphan visits, this is the unrecognized path that was used.
The instant the visit was recorded, in UTC.
true if the visit was classified as a bot based on its User-Agent.The device platform —
android, ios, or desktop — inferred from the User-Agent.The operating system name inferred from the User-Agent (e.g.
windows, macos, linux). null if the OS could not be determined.The browser name inferred from the User-Agent (e.g.
chrome, safari). null if the browser could not be determined.The raw User-Agent header string from the request.
The raw
Referer header value. null if the header was absent.The final URL this visit was redirected to, after rule evaluation.
null for tree links or when the link was archived.The query string forwarded to the destination, if the link has query forwarding enabled. Represented as
Record<string, string[]>. null if not forwarded.Orphan visits — those with
link_id: null — are visible in the raw log with orphan=true. These include requests to unknown slugs, archived links, and the root path of a domain. The web UI surfaces orphans separately; in the API they are part of the same flat log. Use the orphan=true filter to isolate them, or bot=false alongside it to see only human orphan traffic.