Read a subject's activity

The newest entries recorded against one subject, limit at a time (50 by default, 200 at most), newest first. Name the subject by alias and id:

curl "https://api.subscriby.net/v1/activity?subject_type=project&subject_id=$PROJECT_ID&limit=20" \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"

There is no paging beyond limit: the endpoint is a recent-history read, not an export. The subject is resolved through its own tenant-scoped query before activity is read, so passing the id of a project (or subscription, plan, member) that belongs to another team returns 404 RESOURCE_NOT_FOUND rather than an empty list; existence never leaks across tenants.

• subject_type and causer_type use short morph aliases (project, project-subscription, project-subscription-plan, project-user, project-resource, user, …) rather than internal class names. Treat them as opaque strings. The subject_type query parameter accepts only the aliases listed on the endpoint; a class name is 422 VALIDATION_FAILED.
• actor_kind distinguishes the surface the change came through: human (dashboard click), api_token (REST), mcp (MCP tool), zapier, webhook, system (scheduled job). Filter on it client-side when you need "everything the agent did yesterday" separately from dashboard clicks.
• properties keys matching token, secret, password, api_key or api_secret (case-insensitive) are stripped at any depth before the response leaves the server, so LLM context windows never see credentials that were logged alongside a write.