Pagination Support for Action Runs Endpoint and Audit Log Support for Runs
R
Ron Kim
Currently, the
GET https://api.port.io/v1/actions/runs/:run_id/logs
endpoint is limited to returning up to 1000 records and does not support pagination. While polling the endpoint frequently can reduce the risk of missing records, this is not an ideal or scalable design for systems that rely on action run history for monitoring, auditing, or external integrations. In high-activity environments, the lack of pagination makes it difficult to reliably retrieve the full history of runs, especially when building automation, alerting, or observability pipelines on top of Port APIs.We would like to request one of the following improvements:
- Add pagination support to the action runs endpoint(as well as the audit logs API), so clients can safely retrieve the full result set without being limited to 1000 records.
- Additionally, make action runs available through the audit log API for long-term monitoring and external integrations.
Having these options would allow teams to build reliable monitoring and alerting workflows without needing to poll aggressively or risk missing records.