What reports are available in Notory?

Requires Pro

Quick answer

Notory doesn’t ship fixed standard reports. Instead, you build your own saved reports: a report is a saved analysis of one object type from your Flexible data (Catalog) — with optional grouping, a metric (count, sum, or average), and freely chosen columns for the CSV export. You’ll find the module under Reports in the left-hand navigation.

Prerequisites

Required role Logged-in user with access to the Reports module

— Any logged-in user of the tenant can create, run, and export reports. Programmatically, the API token needs valid access to the tenant.

Reports are part of the Flexible data module and are unlocked via the custom_fields feature — in other words, a Pro feature. Without a matching plan, the API responds with 403. Because a report runs on your own object types (records), you first need at least one object type with records in the Catalog.

Overview

GUI (web interface)

1. Open the “Reports” module. Select Reports in the left-hand navigation. At the top, use “New report” to create a new report; the reports you’ve already saved appear below.

   Screenshot pending berichte-uebersicht-01 Reports module with the 'New report' button and a list of saved reports

   The Reports module with the creation area and the saved reports.

2. The building blocks of a report. Every report consists of: an object type (what’s being analyzed), a grouping (which field results are bundled by), a metric (Count, Sum, or Average — for sum/average, over a number field), and the columns used for the export.

API (curl)

The module lives at /api/v1/reports. An overview of the saved reports:

List reports

curl -H "Authorization: Bearer inv_dein_token" \
  https://demo.notory.io/api/v1/reports

Response (excerpt)

[
  {
    "id": "018f7d10-2a3b-7c4d-8e5f-6a7b8c9d0e1f",
    "name": "Verträge nach Status",
    "description": null,
    "object_type": "vertrag",
    "config": {
      "group_by": "status",
      "metric": "count",
      "columns": ["name", "status", "kosten"]
    },
    "schedule": null,
    "created_at": "2026-07-08T09:30:00Z",
    "updated_at": "2026-07-08T09:30:00Z"
  }
]

If the custom_fields feature isn’t included in the plan, the API responds with 403.

What happens behind the scenes?

• License gate (Pro via custom_fields): The entire Reports module depends on the custom_fields feature. Without it, you get 403 — not because of a dedicated “Reports” permission, but because reports are part of Flexible data.
• Analyzes records, not assets: A report reads records of one of your own object types (Catalog), not built-in assets. So object_type must be an object type from your flexible-data platform.
• Your tenant only: Only records from your own tenant are analyzed; deleted ones (deleted_at) are excluded.
• A saved definition: A report only stores the build definition (object type, grouping, metric, filters, columns) — the numbers are only produced when you run it.

Related topics

• Create & export a report
• Set up recurring reports
• Catalog — your own object types & records
• Import & Export — export assets as CSV/JSON
• API introduction