# GraphQL Pagination Endpoint Probe (`junipr/graphql-pagination-smoke-tester`) Actor

Smoke-test GraphQL pagination behavior by running bounded cursor, offset, or page-based query sequences and detecting unstable cursors, duplicates, missing page info, empty pages, and response-shape issues.

- **URL**: https://apify.com/junipr/graphql-pagination-smoke-tester.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** SEO tools, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.50 / 1,000 schema validateds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## GraphQL Pagination Endpoint Probe

### Store Positioning

**Store title:** GraphQL Pagination Endpoint Probe

**Short description:** Smoke-test GraphQL pagination behavior by running bounded cursor, offset, or page-based query sequences and detecting unstable cursors, duplicates, missing page info, empty pages, and response-shape issues.

**SEO title:** GraphQL Pagination Endpoint Probe — API, schema, and developer QA

**SEO description:** Smoke-test GraphQL pagination behavior by running bounded cursor, offset, or page-based query sequences and detecting unstable cursors, duplicates, missing page info, empty pages, and response-shape issues. Use it to catch contract drift, schema mistakes, unsafe endpoint assumptions, and developer-tool quality issues before release.

**Categories:** SEO\_TOOLS, DEVELOPER\_TOOLS

**Keywords:** graphql, pagination, smoke, tester, api/developer qa

### Pay-Per-Event Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

- Tier: A1 — API/developer QA
- Primary event: `schema-validated` at $0.00650 base
- Default max charge: $10.00
- Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

- `actor-start`: base $0.00500, GOLD $0.00400. Graphql Pagination Smoke Tester: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `schema-validated`: base $0.00650, GOLD $0.00520. Graphql Pagination Smoke Tester: charged when schema validated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `contract-rule-checked`: base $0.00390, GOLD $0.00312. Graphql Pagination Smoke Tester: charged when contract rule checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `report-generated`: base $0.05000, GOLD $0.04000. Graphql Pagination Smoke Tester: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

### Public Task Concepts

- Audit GraphQL Pagination Endpoint Probe controls on a capped public sample
- Find high-priority GraphQL Pagination Endpoint Probe issues before release
- Validate GraphQL Pagination Endpoint Probe evidence from supplied pages
- Prioritize GraphQL Pagination Endpoint Probe fixes with severity and proof
- Export GraphQL Pagination Endpoint Probe QA rows for client review

Runs bounded local GraphQL pagination endpoint readiness checks from mock page samples, tracking cursors, offsets, duplicate item IDs, pageInfo health, GraphQL errors, and pass/fail status.

### Inputs

- `endpointUrl`
- `headers`
- `operationDocument`
- `operationName`
- `initialVariables`
- `paginationStrategy`
- `itemsPath`
- `pageInfoPath`
- `cursorVariableName`
- `offsetVariableName`
- `pageSizeVariableName`
- `maxPages`
- `requestDelayMs`
- `includeResponseSamples`
- `timeoutMs`
- `maxChargeUsd`

### Outputs

Dataset fields: `endpointUrl`, `operationName`, `paginationStrategy`, `pageIndex`, `requestCursor`, `nextCursor`, `requestOffset`, `hasNextPage`, `itemCount`, `duplicateItemCount`, `firstItemId`, `lastItemId`, `responseTimeMs`, `graphqlErrorCount`, `issueCode`, `warning`, `passed`.

Reports: `graphql-pagination-smoke-test-report.md`, `pagination-page-results.csv`, `cursor-flow.json`, `duplicate-items.csv`, `graphql-pagination-errors.json`.

Use small capped runs first; live network checks should stay bounded and avoid secrets in inputs.

Live and local execution use the same pay-per-event billing guard: the actor-start event is accepted before analysis, each paid row is charged before dataset output, reports are charged before key-value-store output, and `maxChargeUsd` stops gracefully without leaking unpaid artifacts.

# Actor input Schema

## `endpointUrl` (type: `string`):

Public endpoint URL to fetch or inspect for GraphQL Pagination Endpoint Probe.

## `headers` (type: `object`):

Optional request headers for authorized endpoints. Avoid secrets in shared examples and public tasks.

## `operationDocument` (type: `string`):

Operation Document controls GraphQL Pagination Endpoint Probe processing for the supplied inputs; keep values conservative for first runs.

## `operationName` (type: `string`):

Operation Name controls GraphQL Pagination Endpoint Probe processing for the supplied inputs; keep values conservative for first runs.

## `initialVariables` (type: `object`):

Initial Variables controls GraphQL Pagination Endpoint Probe processing for the supplied inputs; keep values conservative for first runs.

## `mockPages` (type: `array`):

Mock Pages controls GraphQL Pagination Endpoint Probe processing for the supplied inputs; keep values conservative for first runs.

## `paginationStrategy` (type: `string`):

Pagination Strategy controls GraphQL Pagination Endpoint Probe processing for the supplied inputs; keep values conservative for first runs.

## `itemsPath` (type: `string`):

Items Path controls GraphQL Pagination Endpoint Probe processing for the supplied inputs; keep values conservative for first runs.

## `pageInfoPath` (type: `string`):

Page Info Path controls GraphQL Pagination Endpoint Probe processing for the supplied inputs; keep values conservative for first runs.

## `cursorVariableName` (type: `string`):

Cursor Variable Name controls GraphQL Pagination Endpoint Probe processing for the supplied inputs; keep values conservative for first runs.

## `offsetVariableName` (type: `string`):

Offset Variable Name controls GraphQL Pagination Endpoint Probe processing for the supplied inputs; keep values conservative for first runs.

## `pageSizeVariableName` (type: `string`):

Page Size Variable Name controls GraphQL Pagination Endpoint Probe processing for the supplied inputs; keep values conservative for first runs.

## `maxPages` (type: `number`):

Maximum pages to process in one run; keep defaults low for safe first runs.

## `requestDelayMs` (type: `number`):

Request Delay ms controls GraphQL Pagination Endpoint Probe processing for the supplied inputs; keep values conservative for first runs.

## `includeResponseSamples` (type: `boolean`):

Include response samples in output rows or reports when available.

## `timeoutMs` (type: `number`):

Maximum time in milliseconds allowed for the GraphQL Pagination Endpoint Probe operation before it is treated as timed out.

## `maxChargeUsd` (type: `number`):

Maximum estimated PPE charge allowed for the run before the actor stops gracefully.

## Actor input object example

```json
{
  "endpointUrl": "https://rickandmortyapi.com/graphql",
  "headers": {},
  "operationDocument": "query Characters($page: Int) { characters(page: $page) { info { next pages } results { id name status } } }",
  "operationName": "Characters",
  "initialVariables": {
    "page": 1
  },
  "mockPages": [],
  "paginationStrategy": "offset",
  "itemsPath": "data.characters.results",
  "pageInfoPath": "data.characters.info",
  "cursorVariableName": "cursor",
  "offsetVariableName": "page",
  "pageSizeVariableName": "first",
  "maxPages": 2,
  "requestDelayMs": 0,
  "includeResponseSamples": true,
  "timeoutMs": 10000,
  "maxChargeUsd": 1
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/graphql-pagination-smoke-tester").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/graphql-pagination-smoke-tester").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call junipr/graphql-pagination-smoke-tester --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/graphql-pagination-smoke-tester"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/3ubrYbwyxBq3Jl1Mq/builds/g4qN4tB44b8RcWMAd/openapi.json