Analytics API on AuthOS Docs | Auth Operating System API and SDK Guides

Analytics Endpoint Reference

Mon, 01 Jan 0001 00:00:00 +0000

GET /api/organizations/:org_slug/analytics/login-trends

Retrieve daily login counts grouped by date. This endpoint returns a time series of authentication events, useful for visualizing login activity trends over time.

Authentication: Required (JWT)

Permissions: Must be a member of the organization (any role: Owner, Admin, or Member)

Path Parameters:

Parameter	Type	Description
`org_slug`	string	Organization slug

Query Parameters:

Parameter	Type	Required	Default	Description
`start_date`	string	No	30 days ago	Start date in `YYYY-MM-DD` format
`end_date`	string	No	Today	End date in `YYYY-MM-DD` format

Request Headers:

Analytics Dashboard Recipes

Mon, 01 Jan 0001 00:00:00 +0000

Best Practices

Date Range Selection

# Last 7 days
curl "https://sso.example.com/api/organizations/acme-corp/analytics/login-trends?start_date=$(date -u -d '7 days ago' +%Y-%m-%d)&end_date=$(date -u +%Y-%m-%d)" \
  -H "Authorization: Bearer eyJhbGc..."

# Current month
START_DATE=$(date -u +%Y-%m-01)
END_DATE=$(date -u +%Y-%m-%d)
curl "https://sso.example.com/api/organizations/acme-corp/analytics/login-trends?start_date=$START_DATE&end_date=$END_DATE" \
  -H "Authorization: Bearer eyJhbGc..."

Combining Multiple Analytics

# Fetch all analytics data in parallel for a dashboard
ORG="acme-corp"
TOKEN="eyJhbGc..."
BASE_URL="https://sso.example.com"

curl "$BASE_URL/api/organizations/$ORG/analytics/login-trends" \
  -H "Authorization: Bearer $TOKEN" &

curl "$BASE_URL/api/organizations/$ORG/analytics/logins-by-service" \
  -H "Authorization: Bearer $TOKEN" &

curl "$BASE_URL/api/organizations/$ORG/analytics/logins-by-provider" \
  -H "Authorization: Bearer $TOKEN" &

curl "$BASE_URL/api/organizations/$ORG/analytics/recent-logins?limit=20" \
  -H "Authorization: Bearer $TOKEN" &

wait

Pagination for Large Result Sets

For recent logins with high volume:

Analytics Security and Operations

Mon, 01 Jan 0001 00:00:00 +0000

Analytics endpoints require a current bearer JWT and organization membership. Treat login events as sensitive operational data and expose them only to users whose role and product duties require them.

Operating boundaries

The default date window is 30 days; send explicit dates for reproducible reports.
Dates with no activity may be omitted rather than returned with a zero count.
Recent-login events are ordered newest first and are immutable historical records.
The recent-login limit is not offset pagination. Do not assume one response is a complete export.
Provider and service counts describe recorded authentication events, not unique active users.
Protect exported identifiers and timestamps according to your retention and access policy.

Production practices

Use bounded date ranges for charts and scheduled reports.
Cache only for an explicitly defined freshness interval.
Label time zones and report windows in dashboards.
Monitor unusual spikes, but confirm application releases and traffic changes before treating them as incidents.
Use audit logs for administrative changes; analytics events serve a different purpose.

Analytics Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Symptom guide

Symptom	Check	Resolution
401 response	Authorization header and JWT validity	Send a current bearer JWT
403 response	Organization membership	Use a member of the requested organization
404 response	Organization slug	Resolve the organization before requesting analytics
An expected day is absent	Date window and whether that day had events	Send explicit UTC dates and treat omitted dates as zero only when appropriate
Service/provider count looks low	Selected window and how authentication events are recorded	Compare the same explicit period and verify the expected login path emitted events
Recent results are incomplete	Requested `limit` and lack of offset pagination	Use a bounded limit for monitoring; use date-based aggregate endpoints for older periods
Dashboard panels disagree	Different implicit request times or date windows	Compute one window and send it to every compatible request
Dashboard is slow	Range size and parallel query volume	Bound the range, cache deliberately, and avoid uncontrolled refresh loops

Log statuses, error codes, and report windows, but never log bearer tokens. See API error handling for resilient client patterns.

Analytics API on AuthOS Docs | Auth Operating System API and SDK Guides

Analytics Endpoint Reference

Login Trends

GET /api/organizations/:org_slug/analytics/login-trends

Analytics Dashboard Recipes

Best Practices

Date Range Selection

Combining Multiple Analytics

Pagination for Large Result Sets

Analytics Security and Operations

Operating boundaries

Production practices

Analytics Troubleshooting

Symptom guide