curl -X POST "https://api.scanova.io/user-logs/export/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{ "fromDate": "01/09/2026 00:00", "toDate": "07/09/2026 23:59" }'
{
"id": 483,
"message": ["User Logs Export is in progress. You will receive an email on completion."]
}
User Logs & Activity
Trigger a user activity log export
POST /user-logs/export/
POST
/
user-logs
/
export
/
curl -X POST "https://api.scanova.io/user-logs/export/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{ "fromDate": "01/09/2026 00:00", "toDate": "07/09/2026 23:59" }'
{
"id": 483,
"message": ["User Logs Export is in progress. You will receive an email on completion."]
}
Queues an asynchronous job that generates a CSV of account activity (create/update/delete events, logins, and shares) for a date range, on the Management API host (
The call returns
api.scanova.io), authenticated with your raw Management API key.
POST https://api.scanova.io/user-logs/export/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
string
Start of the export range, as
DD/MM/YYYY HH:MM (24-hour), exclusive.string
End of the export range, as
DD/MM/YYYY HH:MM (24-hour), inclusive.curl -X POST "https://api.scanova.io/user-logs/export/" \
-H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
-H "Content-Type: application/json" \
-d '{ "fromDate": "01/09/2026 00:00", "toDate": "07/09/2026 23:59" }'
{
"id": 483,
"message": ["User Logs Export is in progress. You will receive an email on completion."]
}
200 immediately once the job is queued — id is the export job’s id in List user log export history, where you poll status. The account receives an email when the export completes or fails.
fromDate/toDate are not validated synchronously. A malformed date string doesn’t produce a 400 here — the job is created and only fails asynchronously once the worker attempts to parse it, ending in status: "failed" and a failure email. Always double-check the DD/MM/YYYY HH:MM format before sending.403 if the account’s plan lacks the USER_LOGS_EXPORT quota, or if a shared user calling this lacks the SHARED_USER_CAN_EXPORT_USER_LOGS permission:
403
{ "detail": "Your plan does not have user logs quota." }
Completed export records and their CSV files are retained for 14 days, after which they’re purged automatically.
Related
- List user log export history — poll job status.
- Delete an export history record — remove a job early.
- Management API overview — the auth scheme and quota rules that apply to this endpoint.
Authorizations
Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: 401f7ac837da42b97f613d789819ff93537bee6a. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. api.scanova.io) — the same key sent to the regular API host will not authenticate.
Response
200 - application/json
Export job queued.
Was this page helpful?