Reports API

8 routes across 2 controllers: the etl-ep (server-to-server access key) routes the backend serves for this family at the commit named in the front matter, plus its read-only public-ep routes, listed one table per controller. How to authenticate, send a body, page a query and read the response envelope is in the Data API reference, and the way in for a new integration is the integration path.

Every path is resolved from the controller’s mapping annotations; nothing here describes behaviour, because nothing about behaviour has been read — the table is what the backend serves and no more. backoffice-ep routes (the platform’s own applets, with a signed-in user’s token) and anonymous write routes are not listed; what the family serves on backoffice-ep only, and how many of its routes carry no access segment at all, is at the end of the page. A path missing from this page is not a path your access key is refused — see which reference to read.

Sales reports

ReportFinancialCubeMonthlySalesByProductSalesmanController

7 routes under /core2/tnt/dm/erp/reports/monthly-sales-product-salesman (ReportFinancialCubeMonthlySalesByProductSalesmanController.java).

ReportSalesTotalSoldItemsQuantityController

1 route under /core2/tnt/dm/erp/reports/sales/total-sold-items-qty (ReportSalesTotalSoldItemsQuantityController.java).

What this family does not expose over etl-ep

What follows is grouped by URL convention, and the convention does not decide which credential is accepted. The backend falls back in both directions: an etl-ep handler that finds no usable access key tries the bearer token (EndpointMethod.java:300-307), and a route reached with no Authorization header at all falls through to the access-key interceptor (TenantAuthorizationInterceptor.java:74-79). So read these lists as “no documented etl-ep path”, never as “your access key will be refused” — what still decides the outcome is the permission the handler checks.

Controllers in the same family whose routes all sit under backoffice-ep paths:

• BiDashboardBlocksController — 6 backoffice-ep routes (BiDashboardBlocksController.java)
• BiDashboardBlocksHdrController — 6 backoffice-ep routes (BiDashboardBlocksHdrController.java)
• BiDashboardController — 6 backoffice-ep routes (BiDashboardController.java)
• BiDashboardPermissionController — 8 backoffice-ep routes (BiDashboardPermissionController.java)
• BiReportHdrController — 8 backoffice-ep routes (BiReportHdrController.java)
• BiReportPermissionController — 7 backoffice-ep routes (BiReportPermissionController.java)
• BiReportQueryEventHdrController — 8 backoffice-ep routes (BiReportQueryEventHdrController.java)
• BiReportQueryRunOutputHdrController — 8 backoffice-ep routes (BiReportQueryRunOutputHdrController.java)
• BiReportQueryRunHdrController — 7 backoffice-ep routes (BiReportQueryRunHdrController.java)
• BiReportQueryRunOutputFileHdrController — 7 backoffice-ep routes (BiReportQueryRunOutputFileHdrController.java)
• BiReportQueryTemplateHdrController — 7 backoffice-ep routes (BiReportQueryTemplateHdrController.java)
• EntityOutstandingDocumentController — 3 backoffice-ep routes (EntityOutstandingDocumentController.java)
• EntityReportController — 7 backoffice-ep routes (EntityReportController.java)
• FinancialReportController — 3 backoffice-ep routes (FinancialReportController.java)
• JournalPostingController — 8 backoffice-ep routes (JournalPostingController.java)
• GenericDocumentGrossProfitReportController — 1 backoffice-ep route (GenericDocumentGrossProfitReportController.java)
• PurchaseReportController — 5 backoffice-ep routes (PurchaseReportController.java)
• SalesReportMallController — 15 backoffice-ep routes (SalesReportMallController.java)
• SalesReportController — 20 backoffice-ep routes (SalesReportController.java)
• StockReportController — 9 backoffice-ep routes (StockReportController.java)

And 63 routes this page does not count at all. A route reaches the tables and the lists above only when its path carries an access segment; these 63, served by controllers in scope for this page, carry none — the resource sits directly under its base path, with no /etl-ep or /backoffice-ep suffix. By the same fallback an access key reaches them too, so their absence is a limit of the classification, not a statement about what you can call. Six of the resources in that position — chart of accounts, ledgers, cashbooks, suppliers, purchase invoices and payment vouchers — are documented in full on the ERP Core API pages, with request and response bodies verified against the live API.

Related

• Data API — reading the underlying records with a query instead
• API Reference — how many routes exist per family, and which have a page
• Authentication — the access key an etl-ep call carries