Is sounds like you're assuming functionality that may-or-may-not be there.
/jsonapi/my-5-articles is an alias for
items[paging] isn't a query param for pagination, only
page is (with
 options for specifying page size & offsets).
It sounds like what you want, in terms of the JSON API spec, is a paginated compound document (i.e. the
included property that has all your queue nodes for the
items relationship). Per the JSON API spec:
A server MAY choose to limit the number of resources returned in a response to a subset (“page”) of the whole set available.
A server MAY provide links to traverse a paginated data set (“pagination links”).
Pagination links MUST appear in the links object that corresponds to a collection. To paginate the primary data, supply pagination links in the top-level links object. To paginate an included collection returned in a compound document, supply pagination links in the corresponding links object.
It's optional for the JSON API module to supply pagination links. If it does supply them, it will be in the
links document property for the resource you're requesting.
Since you're wanting pagination for included resources, the spec says:
To paginate an included collection returned in a compound document, supply pagination links in the corresponding links object.
I'm assuming "corresponding links object" is different from "top-level links" and they're referring to
links property for objects within the
From a quick look over the JSON API docs/code it doesn't appear to support this functionality. That may or may not be the case, you'll need to see if it does. You should check the project's issue queue.
The specs' flexibility on this scenario means the authors may not have put the functionality in there. If that's the case, you'll need to figure out a workaround or implement your own solution here.