DeltaLead API Cursor-Based Pagination for List Endpoints

The REST API is in early access and is enabled per account on request. API keys are not yet issued from the dashboard. To request access, contact your account executive.

The DeltaLead list endpoint, GET /leads, returns paginated results using cursor-based pagination. Rather than page numbers, the API returns an opaque next_cursor value that encodes your position in the result set. Pass it back as the cursor query parameter to fetch the next page. When has_more is false, you have retrieved all available records.

Pagination Parameters

integer

default:"20"

The number of results to return per page. Minimum: 1. Maximum: 100. Defaults to 20 if omitted.

string

An opaque cursor string returned in the previous response’s next_cursor field. Omit this parameter to start from the beginning of the result set.

Paginated Response Format

Every list endpoint returns results in a data array, with both pagination fields at the root level:

{
  "data": [
    { "id": "lead_abc123", "..." }
  ],
  "next_cursor": "eyJpZCI6ImxlYWRfYWJjMTIzIn0",
  "has_more": true
}

array

The array of resource objects for the current page.

string

Pass this value as the cursor query parameter in your next request to retrieve the following page. This field is null when has_more is false.

boolean

true if additional pages exist beyond this one; false when you have reached the end of the result set.

The response does not include a result total. Counting one would require a second query over the same filter on every page, and no listing on the platform does that. To know whether records remain, has_more is enough.

Iterating All Pages

The example below fetches every lead in your account by looping until has_more is false:

Fetch all leads

async function fetchAllLeads(apiKey) {
  const leads = [];
  let cursor = null;

  do {
    const url = new URL('https://platform-api.deltalead.ai/v1/leads');
    url.searchParams.set('limit', '100');
    if (cursor) url.searchParams.set('cursor', cursor);

    const res = await fetch(url, {
      headers: { Authorization: `Bearer ${apiKey}` }
    });
    const page = await res.json();

    leads.push(...page.data);
    cursor = page.has_more ? page.next_cursor : null;
  } while (cursor);

  return leads;
}

Cursors are opaque strings — do not attempt to parse, decode, or construct them manually. Their internal format may change between API versions without notice. Always use the next_cursor value exactly as returned in the response.

Filtering and Sorting with Pagination

You can combine pagination parameters with any filtering or sorting parameters supported by a given endpoint. Filtering parameters are encoded into the cursor, so you do not need to repeat them on subsequent pages — only the cursor (and optionally limit) are required after the first request.

Set limit=100 when you need to fetch a large number of records. Using the maximum page size minimises the total number of HTTP round-trips required, which reduces both latency and the risk of hitting rate limits. See Rate Limits for details.

Overview

Leads

Webhooks

DeltaLead API Cursor-Based Pagination for List Endpoints

Paginated Response Format

Iterating All Pages

​Pagination Parameters

​Paginated Response Format

​Iterating All Pages

​Filtering and Sorting with Pagination

Pagination Parameters

Paginated Response Format

Iterating All Pages

Filtering and Sorting with Pagination