Pagination

Every list endpoint returns a data array wrapped in a meta + links envelope. Pagination is page-based, capped at 100 rows per request.

Response shapeCopy Anchor Link

{
  "data": [
    { "id": "prj_...", "name": "Research Premium" },
    { "id": "prj_...", "name": "Weekend Studio" }
  ],
  "links": {
    "first": "https://api.subscriby.net/v1/projects?page=1",
    "last": "https://api.subscriby.net/v1/projects?page=4",
    "prev": null,
    "next": "https://api.subscriby.net/v1/projects?page=2"
  },
  "meta": {
    "current_page": 1,
    "from": 1,
    "last_page": 4,
    "per_page": 25,
    "to": 25,
    "total": 92
  }
}

data is ordered by created_at descending (newest first) on every collection endpoint.

The per_page and page parametersCopy Anchor Link

Every collection endpoint accepts:

• per_page — number of rows in the response (default 25, max 100). limit is accepted as an alias on every list that once documented it.
• page — 1-based page index (default 1).

curl "https://api.subscriby.net/v1/projects?per_page=50&page=2" \
  -H "Authorization: Bearer sbt_live_..."

If per_page is omitted, endpoint-specific defaults apply:

Iterating across pagesCopy Anchor Link

async function fetchAllProjects(token: string) {
  const all = [];
  let page = 1;

  while (true) {
    const url = `https://api.subscriby.net/v1/projects?per_page=100&page=${page}`;
    const res = await fetch(url, {
      headers: { Authorization: `Bearer ${token}` },
    });
    const body = await res.json();

    all.push(...body.data);

    if (body.meta.current_page >= body.meta.last_page) break;
    page += 1;
  }

  return all;
}

For very large historical pulls (years of payment / subscription history) prefer streaming over webhooks instead of polling — see Webhook endpoints.

Filtering before paginatingCopy Anchor Link

Combine per_page with the resource-specific filters to avoid pagination loops on large tenants:

curl "https://api.subscriby.net/v1/subscriptions?status=active&per_page=100" \
  -H "Authorization: Bearer sbt_live_..."

Cursor paginationCopy Anchor Link

The REST API does not expose cursors today. The one exception is the MCP list_transactions tool, which uses keyset pagination internally because creators routinely query entire years of payment history. REST callers that need the same data should filter by date range or use MCP directly.

RelatedCopy Anchor Link

• Rate limiting — how hard you can poll.
• Webhook endpoints — streaming alternative to polling.