Port's API has a lot of information that is useful for auditing purposes but much of it is spread out across multiple routes. For example, /v1/audit-log contains the information you see in the audit log UI, /v1/actions/runs contains action metadata, and /v1/users has information around user access. For external Security teams that want to track Port information but don't have in-depth knowledge on how the system works, it would be very useful to collect that information into one route that they can use.