Failed presentations by reason category
Every refused presentation in the period, counted by the category of its reason, read from the check timelines. A check can be refused more than once before it ends, so this counts attempts, not checks. The plan keeps timelines for less time than checks: before retention.eventsFrom the counts are partial. group_by splits each category further. Under a project's key, over its project; under an organisation's key, over every project in it, or one with project_id. UTC days. Any key may call it, of either scope; each key spends its own budget.
Request
- Base URL: https://api.tessio.eu
- URL: https://api.tessio.eu/v1/stats/failures
- Auth: HTTP bearer
Query parameters
The first day, inclusive. A start further back than two years is refused rather than narrowed, so an answer never covers a shorter range than the one asked for.
Omitting both from and to gives the default window, the last 30 days. Omitting only from is a half-written request and is refused.
The last day, inclusive. Defaults to today, and an end in the future is pulled back to today, so a preset like "this year" does not draw empty months that read as an outage.
Live checks, test checks or both. Defaults to live at org scope (an organisation's key included), which is what a customer's own numbers are, and to the project's own mode at project scope (a project's key included), so a test project reads its checks.
Split each category further. method is the profile the check asked for (av or eudiw), which it carries from creation, or for a check from before profiles were recorded, its method; what answered it is written only when it ends, which most refused checks never do. Omit for one row per category.
Only this project of the org. A project of another org is refused exactly as one that does not exist, invalid_project_id. Under a project's key, only that project may be named.
Response
OK