POST /api/v2/metrics/list in the Public API (V2) now supports pagination. Until now, a list query stopped at 1,000 series, and there was no way to fetch the rest. With pagination, you request the list in pages and continue until the last page.
Pagination is optional. The response format stays the same, so existing integrations keep working without changes. Use it when a query matches more series than fit in one page. That usually means a custom metric with high-cardinality tags.
The Limits page in your app shows which custom metrics have the most unique keys. A paginated query that matches more than 100,000 metric keys returns an error instead of partial results. The metrics API documentation describes the request format and shows an example.
Timeseries queries work as before. AppSignal MCP uses the same endpoint, so your agent sees the same data as an unpaginated API request. If you still read metric lists through the deprecated GraphQL API, this is a good time to move. The September changelog entry explains why.
Tell us what you think in our Discord channel.
