New Relic One API ↔ Data Export pagination behavior for large NRQL facet sets

An integration between New Relic One API NRQL queries and Data Export workflows needs a clear contract for completeness when facet cardinality is high.

The One API exposes NRQL via a REST endpoint with query, page and pageSize parameters. Pagination is page-number based with a default pageSize of 100 and a documented maximum of 10,000 per request. Documentation does not explicitly state whether all facet values are returned for high-cardinality FACET clauses, and the only pagination cue described is the presence or absence of a next link.

For export and subsequent restoration scenarios, the unresolved decision is whether large facet sets are automatically paginated across pages or silently truncated by an internal limit. The uncertainty affects how consumers can verify that an exported snapshot contains the full set of facet values.

Does the One API paginate individual facet values across pages when a NRQL query uses a high-cardinality FACET? Is the presence of a next link sufficient to guarantee complete facet coverage for an export, or can facets be dropped within a single page? How should export consumers interpret missing facets when verifying recovered data?