Quick Start
How It Works
| Component | Purpose |
|---|---|
| Activity Logger | Automatically captures events |
| Storage Engine | Persists activity records |
| Query API | Provides paginated access |
| Audit Trail | Maintains complete history |
API Endpoints
Workspace Activity
| Method | Endpoint | Description |
|---|---|---|
GET | /api/v1/workspaces/{ws_id}/activity | List all workspace activity |
Issue Activity
| Method | Endpoint | Description |
|---|---|---|
GET | /api/v1/workspaces/{ws_id}/issues/{issue_id}/activity | List activity for specific issue |
Query Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
limit | int | 50 | Max results per page (1-200) |
offset | int | 0 | Number of results to skip |
Response Schema
Each activity entry follows this structure:| Field | Type | Description |
|---|---|---|
id | string | Unique activity identifier |
workspace_id | string | Workspace where activity occurred |
issue_id | string | Issue ID (for issue activities) |
actor_type | string | "user" or "agent" |
actor_id | string | ID of the actor who performed action |
action | string | Type of action performed |
details | object | Action-specific contextual data |
created_at | string | ISO timestamp of when action occurred |
Tracked Actions
Issue Actions
| Action | Trigger | Details Included |
|---|---|---|
issue.created | Issue creation | title, identifier |
issue.updated | Issue modification | Changed fields and their new values |
Future Actions
The activity log system is designed to capture additional events as the platform grows:- Workspace events (member added/removed)
- Agent executions and results
- File uploads and modifications
- Configuration changes
Usage Examples
Using curl
Python with Filtering
Best Practices
Implement Pagination for Large Datasets
Implement Pagination for Large Datasets
Always use pagination when querying activity logs, especially for active workspaces. The default limit is 50, but you can adjust based on your needs.
Cache Activity Data for Performance
Cache Activity Data for Performance
For frequently accessed activity logs, implement client-side caching to reduce API calls and improve response times.
Filter by Actor Type for Specific Insights
Filter by Actor Type for Specific Insights
Use actor type filtering to separate human actions from automated agent actions for better analysis.
Monitor Activity Patterns for Anomalies
Monitor Activity Patterns for Anomalies
Implement monitoring to detect unusual activity patterns that might indicate issues or security concerns.
Testing
Test the activity log functionality with these commands:Related
Workspace Management
Learn about workspace organization and management
API Authentication
Configure secure API access with tokens

