Skip to main content

EPOS ReportingReport Builder

Overview

Dashboard

Data

Connections
Events
Data purge

Reporting

Hourly reports
Performance reports
End of day reports
Security reports
Calendar

Delivery

Recipients
Schedules & subscriptions
Send history

System

Instance monitor
Themes & templates
Audit & debug
Settings

Details

Dashboard
Connections
Details

New connection

Primary EPOS route. Credentials are sealed and not returned to the browser after save.

Connection details

Friendly label and how the suite reaches your EPOS environment.

Name

API type

Secondary connection (optional)

Use a secondary legacy route when the primary API does not expose a dataset (e.g. voids).

API debug tracingActive

Base URL

Credentials

Stored sealed at rest. Never shown again after save — rotate to replace.

Kappture Integrate uses your API key in the x-api-key header and API key + API secret in POST /auth to obtain a JWT (~24h). Other requests send Authorization: Bearer … and the same x-api-key.

API key

API secret

Optional: legacy JWT only

If this field is filled and API secret is empty, the suite will not call /auth and will use this token until it expires.