List the filter values in the access logs
Returns every country, city, host, server name, log format and ASN the access logs hold, to fill the list filters. It reads the daily aggregates, so values stay listed after their raw lines are gone.
session<token>Session cookie authentication.
Request fulfilled, document follows
application/json- response
The values the access log filters can take, each list sorted.
asns*array<>Sorted by organization, with the ones that have none last.
cities*array<string>countries*array<>Sorted by name.
hosts*array<string>The Host header values the lines carry.
logFormats*array<string>The log formats the lines were read with, such as nginx or traefik-json.
servers*array<string>The server names that recorded access logs.
curl -X GET 'https://geometrikks.example.com/api/v1/access-logs/facets'{ "asns": [ { "asn": 0, "organization": "string" } ], "cities": [ "string" ], "countries": [ { "code": "string", "name": "string" } ], "hosts": [ "string" ], "logFormats": [ "string" ], "servers": [ "string" ]}List access log lines GET
Returns parsed access log lines, newest first, paged with `currentPage` and `pageSize` and sorted with `orderBy` and `sortOrder`. `searchString` matches part of the URL, referrer or user agent, ignoring case unless `searchIgnoreCase` is false. Timings are in seconds, and lines go back ANALYTICS_RAW_RETENTION_DAYS days, 180 by default. For recent polling, use window=10m and deduplicate by id. X-Range-Start and X-Range-End echo inclusive bounds; reuse them as fromTimestamp and toTimestamp on later pages. Do not send window with explicit bounds. Pagination is not a snapshot; overlapping polls can repeat records and do not guarantee late imports or backfills.
Get geo event counts per hour or day GET
Returns geo events and unique IPs, countries and cities for each bucket that has events, oldest first. It reads the hourly or daily aggregates at any range length, so the unique counts are estimates, and those reads count whole hours or UTC days, from the one that holds `startDate` through the last one that starts before `endDate`. With `granularity=daily` and a `tz` other than UTC on a range of 30 days or less, those reads count local days instead. They start at the local midnight of the day holding `startDate` and run through the last hour that starts before `endDate`.