# Paging & filtering to-many relationships

**URL:** <https://discuss.jsonapi.org/t/paging-filtering-to-many-relationships/1833>\
**Category:** Uncategorized\
**Created:** [February 15, 2020, 6:09am UTC](https://discuss.jsonapi.org/t/paging-filtering-to-many-relationships/1833 "2020-02-15T06:09:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![fdrake](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/fdrake/32/654_2.png) [@fdrake](https://discuss.jsonapi.org/u/fdrake)\
**Post date:** [February 15, 2020, 6:09am UTC](https://discuss.jsonapi.org/t/paging-filtering-to-many-relationships/1833/1 "2020-02-15T06:09:43Z")

</div>

When dealing with very to-many large relationships, what are people doing with respect to paging and filtering results? I can see two different approaches:

1. In the relationship, whether included with a resource or retrieved via a relationship’s `self` link, only provide a `related` link that hits a collection that supports whatever filtering and paging is appropriate.

2. Provide filtering and paging directly at the relationship’s `self` link. This can reduce the request count by one, but doesn’t seem to provide substantial benefits.

What are others doing?

-Fred