Pagination And Filtering

List endpoints commonly support pagination and filters. Each endpoint page documents the parameters it accepts.

Pagination parameters

Parameter	Type	Description
`page`	integer	Page number to return. Defaults are documented per endpoint.
`per_page`	integer	Number of records per page. Defaults and maximums are documented per endpoint.

Example:

GET https://valora.spotahome.com/api/v1/c/transactions?page=2&per_page=100
Authorization: Bearer {token}
Accept: application/json

Pagination response

{
  "pagination": {
    "total": 123,
    "per_page": 100,
    "current_page": 2,
    "last_page": 2,
    "from": 101,
    "to": 123
  },
  "data": []
}

Filtering

Filters are passed as query string parameters.

GET https://valora.spotahome.com/api/v1/c/transactions?pay_date_from=2026-01-01&pay_date_to=2026-01-31
Authorization: Bearer {token}
Accept: application/json

Filter conventions

Convention	Example
Date range start	`pay_date_from=2026-01-01`
Date range end	`pay_date_to=2026-01-31`
Amount minimum	`amount_from=100.50`
Amount maximum	`amount_to=500.00`
Exact booking reference	`booking_id=BK123456`

No results

Some endpoints return 404 Not Found when no records match the filters, while still returning an empty data array and pagination metadata. Endpoint pages document this behavior when it applies.

Clients should treat documented no-results responses as a normal empty state, not as an integration failure.