ActivityLog — User Guide
Everything you need to sign up, mint a token, wire your first system into ActivityLog, and bring in Microsoft 365, Azure DevOps, Claude Code, or your own services.
This guide is written for the developer or operator at a customer who has signed up (or is evaluating) ActivityLog. For the marketing pitch see ../Executive-Overview.md; for the formal API contract see ../API-Reference.md; for internal architecture see ../Architecture.md.
Where to start
Sending data into ActivityLog
Not sure which? Start with 50-ingest-native.md — it has the decision tree.
Querying and exporting
| Doc |
Topic |
60-query-api.md |
GET /messages, filters, aggregates, timelines, detail, exports |
Pre-built integrations
Administration
| Doc |
Topic |
80-admin-portal.md |
Admin-portal capabilities for operators (Fyin staff) |
90-reports.md |
Live activity feed, report packs, Grafana — what ships when |
Conventions used in this guide
- Public base URL:
https://api.activitylog.com for the API; https://activitylog.com/portal/ for the customer portal; https://activitylog.com/portal/admin/ for the admin portal. Staging is https://activitylog-api.betawebserver.com / https://activitylog.betawebserver.com/portal/.
- Tokens in examples are placeholders like
al_REPLACE_WITH_YOUR_TOKEN. Never copy these literally — mint your own in the portal.
- Tier numbers quoted in tables come directly from
../Pricing.md. If you spot a drift, that doc is the source of truth.
- Status labels — features marked Live ship today; Coming soon is on the active roadmap; Deferred is acknowledged but not scheduled.
Conventions and tone
- One concept per heading. If a paragraph is long, it's wrong.
- Every command appears in a code block, even one-liners — so you can copy-paste safely.
- Cross-links use relative paths so this folder is portable.
Found a problem?
- API reference drift: file an issue against
../API-Reference.md.
- Pricing-page drift: same, against
../Pricing.md.
- Anything in this guide: open a ticket referencing the file by name.