Pagination

List endpoints use page-number pagination.

Parameter	Type	Default	Allowed
page	integer	1	>= 1
per_page	integer	25	1–100

cURL

curl --fail-with-body --silent --show-error \
  -H "Authorization: Bearer $NUELINK_API_KEY" \
  -H "Accept: application/json" \
  "https://app.nuelink.com/api/public/v1/brands?page=2&per_page=25"

JavaScript

const apiKey = process.env.NUELINK_API_KEY;

const response = await fetch('https://app.nuelink.com/api/public/v1/brands?page=2&per_page=25', {
  headers: {
    Authorization: `Bearer ${apiKey}`,
    Accept: 'application/json',
  },
});

if (!response.ok) {
  throw new Error(`HTTP ${response.status}: ${await response.text()}`);
}

const data = await response.json();
console.log(data);

PHP

<?php

$apiKey = getenv('NUELINK_API_KEY');

$ch = curl_init('https://app.nuelink.com/api/public/v1/brands?page=2&per_page=25');

curl_setopt_array($ch, [
    CURLOPT_HTTPHEADER => [
        "Authorization: Bearer {$apiKey}",
        'Accept: application/json',
    ],
    CURLOPT_RETURNTRANSFER => true,
]);

$response = curl_exec($ch);
$status = curl_getinfo($ch, CURLINFO_RESPONSE_CODE);
curl_close($ch);

if ($status >= 400) {
    throw new RuntimeException("HTTP {$status}: {$response}");
}

echo $response;

Response shape

{
  "status": "success",
  "data": [],
  "pagination": {
    "currentPage": 2,
    "perPage": 25,
    "total": 82,
    "lastPage": 4,
    "nextPageUrl": "https://app.nuelink.com/api/public/v1/brands?page=3",
    "prevPageUrl": "https://app.nuelink.com/api/public/v1/brands?page=1"
  }
}

Use currentPage < lastPage, or nextPageUrl != null, to decide whether another page exists.

Two things that trip people up

A short page is not the last page. Don’t treat “fewer than per_page items” as your only stop condition; use lastPage or nextPageUrl.

An empty data array is still a success. A 200 with "data": [] means nothing matched — the brand has none of that resource, a filter excluded everything, or page is past lastPage. Check pagination.total to tell those apart.

Channels count before they filter

GET /channels calculates total before it drops channels in other states, so one of its pages can be short or even empty while later pages still hold channels. Keep walking until nextPageUrl is null, and don’t use total as the number of channels you’ll receive.

GET /schedule is the one read that isn’t paginated: it returns the whole week in one response.

Walking every page

Keep your filters and page size on each request, and stop on nextPageUrl.

The example reads the base URL from the environment, the same way the Quick Start sets it up:

export NUELINK_API_BASE="https://app.nuelink.com/api/public/v1"

const base = process.env.NUELINK_API_BASE;
const apiKey = process.env.NUELINK_API_KEY;

async function listAll(pathname, params = {}) {
  const items = [];
  let page = 1;

  for (;;) {
    const qs = new URLSearchParams({ ...params, page: String(page), per_page: '100' });
    const response = await fetch(`${base}${pathname}?${qs}`, {
      headers: { Authorization: `Bearer ${apiKey}`, Accept: 'application/json' },
    });

    if (!response.ok) {
      throw new Error(`HTTP ${response.status}: ${await response.text()}`);
    }

    const body = await response.json();
    items.push(...body.data);

    if (body.pagination.nextPageUrl === null) return items;
    page += 1;
  }
}

Two things this guards against. per_page: 100 keeps the request count down, which matters against the 30-per-minute resource limit. And stopping on nextPageUrl rather than on a short page is the only correct termination test.

Post lists also take server-side filters such as view, status, and created_from, so you can often fetch one filtered page instead of walking everything. See Endpoints.

Find a new resource by ID, not by position

Lists come back newest first, but another client can create something between your create and your read. To verify a create, match the id the create returned rather than taking the first item, and walk further pages if it isn’t on page 1.

The page-size parameter is spelled three ways

Surface	Page-size name
REST API	per_page
MCP	perPage
CLI	--per-page

The REST API uses snake_case throughout its paths and query strings; the MCP tools use camelCase and the server translates. If you’re moving code between surfaces, this is the first thing to check.