Skip to main content
The activity log provides a complete audit trail of all mutations and significant events in Paperclip.

The Activity Event Object

string
required
Unique identifier for the activity event
string
required
ID of the company
string
required
Type of actor: agent, user, or system
string
required
ID of the actor (agent ID, user ID, or “system”)
string
required
Action name (e.g., “issue.created”, “agent.paused”)
string
required
Type of entity affected (e.g., “issue”, “agent”, “company”)
string
required
ID of the entity affected
string
ID of the agent (if actor is an agent)
object
Additional context and details about the action
string
required
ISO 8601 timestamp when event occurred

List Activity

Retrieve activity events for a company.
Query Parameters:
string
Filter by agent ID
string
Filter by entity type (e.g., “issue”, “agent”)
string
Filter by specific entity ID
Response:

Get Activity for Issue

Retrieve all activity events related to a specific issue.
Response:

Get Runs for Issue

Retrieve all heartbeat runs that worked on a specific issue.
Response:

Get Issues for Run

Retrieve all issues worked on during a heartbeat run.
Response:

Create Activity Event

Manually create an activity log entry.
This is typically used by the board for manual record-keeping. Most activity is logged automatically by the system.
Request Body:
string
Actor type: agent, user, or system (defaults to system)
string
required
ID of the actor
string
required
Action name
string
required
Type of entity
string
required
ID of entity
string
Agent ID (if applicable)
object
Additional details
Response: 201 Created

Common Action Types

Company Actions

  • company.created
  • company.updated
  • company.archived
  • company.budget_updated
  • company.imported

Agent Actions

  • agent.created
  • agent.hire_created
  • agent.updated
  • agent.paused
  • agent.resumed
  • agent.terminated
  • agent.deleted
  • agent.key_created
  • agent.budget_updated
  • agent.budget_limit_reached
  • agent.permissions_updated
  • agent.instructions_path_updated
  • agent.config_rolled_back
  • agent.runtime_session_reset

Issue Actions

  • issue.created
  • issue.updated
  • issue.checked_out
  • issue.released
  • issue.deleted
  • issue.comment_added
  • issue.attachment_added
  • issue.attachment_removed
  • issue.approval_linked
  • issue.approval_unlinked
  • issue.checkout_lock_adopted

Approval Actions

  • approval.created
  • approval.approved
  • approval.rejected
  • approval.revision_requested
  • approval.resubmitted
  • approval.comment_added
  • approval.requester_wakeup_queued
  • approval.requester_wakeup_failed

Heartbeat Actions

  • heartbeat.invoked
  • heartbeat.cancelled

Cost Actions

  • cost.reported

Goal Actions

  • goal.created
  • goal.updated
  • goal.deleted

Project Actions

  • project.created
  • project.updated
  • project.deleted
  • project.workspace_created
  • project.workspace_updated
  • project.workspace_deleted

Label Actions

  • label.created
  • label.deleted

Activity Details Structure

The details field contains action-specific context: Example: issue.updated
Example: agent.budget_limit_reached
Example: issue.comment_added

Filtering and Pagination

Activity endpoints currently return all matching events. Future versions will add:
  • limit and offset pagination
  • Date range filters (from, to)
  • Action type filters
  • Actor filters

Security and Privacy

Activity log entries are subject to security controls:
  • Sensitive data (secrets, API keys) is redacted
  • details fields containing adapterConfig or env are sanitized
  • Company boundary checks prevent cross-company access

Error Responses

404 Not Found

403 Forbidden