The audit logs enable organization admins to efficiently track member activity, providing detailed records of who performed each action, what was done, and when it occurred.
Activity logs provide a record of actions initiated within your organization, including actions performed through the UI, via the API, or triggered automatically by the system (e.g., automated billing operations).
Access to the activity log is limited to paid tiers:
Only organization admins can access Activity Logs through the Developers Console. To view the logs:
Activity logs in the Developers Console
Only organization admins can access Activity Logs through the Developers Console. To view the logs:
Activity logs in the Developers Console
Each activity log includes a set of properties that provide context about the recorded action:
plan.updated
, customer.created
, invoice.drafted
);Wallet
, Invoice
, Customer
);invoice_id
, customer_id
);front
– triggered from the UIapi
– triggered from the APIsystem
– triggered automatically by the system (e.g., billing)In addition to the above, the Activity Payload section provides contextual data:
All of the fields listed above can be used to filter activity logs, either through the UI or via the API.
In the UI, you can view activity logs for a specific object by clicking on the desired object (e.g., a specific customer, plan, invoice, etc.), and access the Activity Logs tab.
API logs offer a comprehensive record of all API requests and calls made within your organization. They serve as an essential tool for monitoring activity, troubleshooting issues, and auditing system usage.
POST
, PUT
, and DELETE
requests are currently recorded in the API logs. All GET
requests are excluded at this time.POST /api/v1/events
or POST /api/v1/batch_events
, are intentionally omitted from logging to ensure performance and scalability.Access to the API requests logs is limited to paid tiers:
Only organization admins can access API Logs through the Developers Console. To view the logs:
API logs in the Developers Console
Only organization admins can access API Logs through the Developers Console. To view the logs:
API logs in the Developers Console
Each API log includes a set of properties that provide context about the recorded action:
POST
, PUT
, DELETE
);RubySDK
, PythonSDK
or PostmanRuntime/7.44.1
); and200
, 400
, 404
).In addition to the above, the Event Payload section provides contextual data:
All the fields described above can be used to filter API logs, either through the UI or programmatically via the API. Here are som key filtering behaviors to note:
Exact Path Matching: Supplying a full, exact path (e.g., /api/v1/customers
) will return only requests made to that specific endpoint. It will not include requests to extended paths like /api/v1/customers/123
.
Wildcard Path Matching: You can use wildcard patterns (e.g., /api/v1/customers/*
) to match all sub-paths related to a resource. This is useful for retrieving all activity tied to specific objects or nested routes.