Zum Hauptinhalt springen
GET
/
export
/
customData
Export custom client reports
curl --request GET \
  --url https://demo.enneo.ai/api/mind/export/customData \
  --header 'Authorization: Bearer <token>'
[
{
"id": 1,
"type": "login",
"createdAt": "2024-01-15T10:30:00Z",
"customerId": 12345
},
{
"id": 2,
"type": "purchase",
"createdAt": "2024-01-14T15:45:00Z",
"customerId": 12345
}
]

Autorisierungen

Authorization
string
header
erforderlich

JWT-based authentication

Abfrageparameter

format
enum<string>
Standard:As configured in the settings

The format of the export

Verfügbare Optionen:
xlsx,
csv,
json
exportId
integer | null

The ID of the export configuration to use. This corresponds to the index in the customDataExports settings array. If null, the default export as configured in the customDataExportSelected setting will be used.

{parameterName}
string

Dynamic parameters that replace placeholders in the SQL query.

Any parameter defined in the export configuration can be overridden via GET parameters. Parameter names should match the placeholders in the SQL query (without the curly braces).

Parameter Resolution Logic:

  1. If provided as GET parameter → use that value
  2. If not provided but has default value → use default value
  3. If not provided and no default → throw error (parameter required)

Common Parameter Examples:

  • limit=100 → replaces {limit} placeholder
  • offset=0 → replaces {offset} placeholder
  • customerId=12345 → replaces {customerId} placeholder
  • startDate=2024-01-01 → replaces {startDate} placeholder
  • endDate=2024-12-31 → replaces {endDate} placeholder
  • status=active → replaces {status} placeholder
  • departmentId=5 → replaces {departmentId} placeholder

Antwort

Successful operation

Beispiel:
[
{
"id": 1,
"type": "login",
"createdAt": "2024-01-15T10:30:00Z",
"customerId": 12345
},
{
"id": 2,
"type": "purchase",
"createdAt": "2024-01-14T15:45:00Z",
"customerId": 12345
}
]