Pagination and filtering

Cursor pagination

Four operations return a page at a time instead of the full collection:

Method	Path
GET	/properties/{country}/{cadastreId}/transactions
GET	/properties/{country}/{cadastreId}/building-permits
GET	/companies/{scheme}/{id}/properties
GET	/areas/{country}/{areaId}/land-allocations

Each takes two query parameters:

• pageSize: items per page, 1 to 100, default 50.
• pageToken: the opaque cursor from the previous page's nextPageToken.

curl "https://data.placepoint.no/properties/NO/0301-208-15-0-0/transactions?pageSize=25" \
  -H "Authorization: Bearer $TOKEN"

{
  "items": [ /* ... */ ],
  "nextPageToken": "eyJvZmZzZXQiOjF9"
}

Pass nextPageToken back verbatim as pageToken to fetch the next page. It is absent when there is no next page. An empty result is 200 with items: [], never 404.

Cursors are opaque: don't decode or construct one by hand, and don't assume the encoding is stable across releases.

No other query parameters, by design

Every other operation takes no query parameters at all. This is deliberate: a lookup like GET /properties/{country}/{cadastreId}/owners is a path resource, not a filterable list, so there is nothing to filter, sort or search by. If you need a subset of a resource's fields, request the resource and select client-side; the API does not support sparse fieldsets or a ?filter= syntax.