Tino Developers
GET/v1/service/@id/waf/zones/@zone/events

List a website's events

Newest events first. Query: action, from, to (RFC 3339), cursor, limit; meta.next_cursor gives the next page.

API v1 · Updated 2026-10-21View .md

Call it through the gateway https://api.tino.vn/v1 with a token that has the waf:read scope; see Calling the Tino API.

Authentication

Send the token in the header Authorization:

Authorization: Bearer <token>

Tokens that can call it: app tokens (tinoat_, Sign in with Tino) or personal API tokens (tinopat_).

Scopes

waf:read

Parameters

Path parameters

NameTypeRequiredDescription
idintRequiredService ID
zonestringRequiredWebsite ID (UUID) on TinoWAF

Query

NameTypeRequiredDescription
actionstringOptionalOnly events with this action: `block`, `challenge`, `rate_limited` or `log`.
fromstringOptionalStart time, RFC 3339 (e.g. `2026-10-27T00:00:00+07:00`).
tostringOptionalEnd time, RFC 3339.
cursorstringOptional`meta.next_cursor` of the previous page.
limitintegerOptionalEvents per page.

Response

No live sample: the route changes real data or the test account has no data for it. The answer is a JSON object; errors follow the common shape in Calling the Tino API.

Error codes

Error codeDescription
401 · invalid_tokenThe token is wrong, expired or revoked.
403 · insufficient_scopeThe token lacks the waf:read scope.
403 · ip_not_allowedA personal API token called from an IP outside its allow-list.

Business errors of a route usually come as HTTP 200 with {"error": ["<code>"]}; see common error codes.