Pagination and filtering

Alution Cloud does not apply one global pagination rule. Each endpoint description states whether it returns a plain collection or a paginator.

Standard list endpoints

Many GET collection endpoints return the complete filtered collection by default. Where supported, perPage opts into pagination and limit caps an unpaginated result. Do not assume page or per_page works on a standard list unless that endpoint documents it.

Common query parameters include sort, direction, search, with, and resource-specific filters. Unsupported parameters may be ignored.

Paginated responses

Paginated resources use this shape:

{
  "data": [],
  "links": {
    "first": "...",
    "last": "...",
    "prev": null,
    "next": "..."
  },
  "meta": {
    "current_page": 1,
    "from": 1,
    "last_page": 4,
    "path": "...",
    "per_page": 25,
    "to": 25,
    "total": 88
  }
}

Plain collections are returned as JSON arrays or as the resource wrapper shown by that endpoint; they do not invent links or meta.

QUERY endpoints

HTTP QUERY endpoints accept a JSON query model. Their pagination keys belong to that request body—commonly page and per_page—and are separate from the perPage query parameter used by some GET endpoints. Use an HTTP client or proxy that preserves the QUERY method and request body.