Pagination and filtering

Page through collections

Choose page and limit values

Collection endpoints accept page and limit when the operation defines them. Pages start at 1. Use a small limit while developing, then choose a limit that fits your service's memory and latency budget.

Fetch the second page of newest unanswered opinions.

import { opinions } from '@orvelt/business';

const result = await opinions.list({
  projectId: 'PROJECT_ID',
  page: 2,
  limit: 50,
  sort: 'newest',
  responseStatus: 'unresponded',
});

curl --request GET \\
  --url "$ORVELT_API_BASE_URL/project/PROJECT_ID/opinions?page=2&limit=50&sort=newest&responseStatus=unresponded" \\
  --header "x-api-key: $ORVELT_BUSINESS_API_KEY"

Combine supported filters

Only send query fields defined by the operation. For example, goals.list accepts page and limit, while opinions.list also accepts text, date, sort, and response filters.

Date filters

Use epoch-millisecond boundaries

Review and answer list operations use epoch milliseconds for dateFrom and dateTo:

const dateFrom = Date.parse('2026-01-01T00:00:00Z');
const dateTo = Date.parse('2026-02-01T00:00:00Z');

Pass those numbers as query values. Keep the timezone conversion in your application so repeated exports use the same range.