Pagination

Every list endpoint in the FinDesk API returns a paginated response. The shape is the standard Laravel paginator JSON — a data array plus links and meta blocks describing position within the result set.

• Page size
• Navigating pages
• Ordering

Page size#

List endpoints return 100 records per page by default and use that as a fixed size. The size is set server-side; sending a per_page query parameter has no effect today.

Endpoints that paginate include (across both versions):

• GET /applications
• GET /people
• GET /organisations
• GET /leads
• GET /quotes
• GET /enterprises
• GET /users

Navigating pages#

Pass the page query parameter to request a specific page:

GET /api/v2/applications?page=2 HTTP/1.1
Host: app.findesk.com.au
Accept: application/json
Authorization: Bearer 4|GxR9...
X-Enterprise-Id: 1f8a9b2c-...-9e0f

The response includes ready-to-follow URLs under links and structural metadata under meta:

{
  "data": [ /* up to 100 records */ ],
  "links": {
    "first": "https://app.findesk.com.au/api/v2/applications?page=1",
    "last":  "https://app.findesk.com.au/api/v2/applications?page=17",
    "prev":  "https://app.findesk.com.au/api/v2/applications?page=1",
    "next":  "https://app.findesk.com.au/api/v2/applications?page=3"
  },
  "meta": {
    "current_page": 2,
    "from": 101,
    "to": 200,
    "last_page": 17,
    "path": "https://app.findesk.com.au/api/v2/applications",
    "per_page": 100,
    "total": 1623
  }
}

links.next is null on the final page; links.prev is null on page one.

Ordering#

List endpoints return records newest first (created_at DESC). The ordering is fixed — there is no sort parameter today, so iterating pages in order walks the entire result set without duplicates as long as no new records are inserted while you page.

If records are being created while you iterate, prefer fetching the full result set in a single tight loop, or filter by a stable created_at window so newer rows do not push your cursor forward.