Activity Export

The activity export endpoint gives you a full, machine-readable record of every request made under your account — model used, token counts, DA cost, timestamp, and request ID. Use it for billing reconciliation, cost attribution, compliance audits, or feeding into your own analytics stack.

Endpoint#

GET /api/analytics/export

Session-authenticated (requires a valid browser session cookie). This is a dashboard endpoint, not an inference endpoint — it does not accept an Authorization: Bearer API key, and it is not prefixed with /v1.

Downloading an export#

Exports are downloaded from the dashboard: go to Dashboard → Analytics → Export, pick your date range and any filters, and download the CSV. The file streams directly; for large date ranges the download may take a few seconds.

For a programmatic view with your API key, use the activity API instead — see Programmatic alternative below.

Query parameters#

CSV columns#

Processing the export in Python#

Once you have downloaded the CSV from the dashboard, process it locally:

import csv

def load_export(path: str) -> list[dict]:
    with open(path, newline="") as f:
        return list(csv.DictReader(f))

rows = load_export("june-activity.csv")

# Total spend in DA (total_cost is micro-DA: 1 DA = 1,000,000 micro-DA)
total_da = sum(int(r["total_cost"]) for r in rows) / 1_000_000
print(f"Total spend: {total_da:.2f} DA")

# Spend by model
from collections import defaultdict
by_model = defaultdict(int)
for r in rows:
    by_model[r["model"]] += int(r["total_cost"])
for model, micro in sorted(by_model.items(), key=lambda x: -x[1]):
    print(f"  {model}: {micro / 1_000_000:.2f} DA")

Programmatic alternative: the activity API#

If you need usage data over the API rather than a dashboard download, GET /v1/activity is key-authed with your regular sk- key and returns the last 30 days as daily rollups — one row per day × model, with date, model, model_permaslug, endpoint_id, provider_name, prompt_tokens, completion_tokens, requests, and usage (DA spent). Pass ?date=YYYY-MM-DD to narrow to a single day.

curl "https://opendunes.com/api/v1/activity?date=2026-06-30" \
  -H "Authorization: Bearer $OPENDUNES_API_KEY"

The activity API is daily rollups only; request-level rows come from the CSV export above. See Control Costs with the Analytics API for full examples.

Reconciling with your balance#

The summed total_cost in the export for a given period should match the debits shown in your balance history on your dashboard exactly — costs are integer micro-DA, so there is no rounding drift. If they differ, file a support request with the export file and the date range.

Compliance and auditing#

Every API response carries an X-Request-Id header (UUID-v7). If you log it on your side, you can join your application logs to the export rows by timestamp and model for a complete audit trail.

For applications subject to Algeria's Law 18-07, the export provides the token-level usage records required for data processing accountability documentation.

Scheduled exports#

To automate monthly exports, run a script on a cron schedule:

# Export the previous month's activity on the 1st of each month
0 2 1 * * python3 /opt/scripts/export_activity.py $(date -d "last month" +\%Y-\%m-01) $(date -d "last day of last month" +\%Y-\%m-\%d)