# Generic relationships linked to heterogeneous resources

**URL:** https://discuss.jsonapi.org/t/generic-relationships-linked-to-heterogeneous-resources/2480
**Category:** Uncategorized
**Created:** [July 26, 2022, 10:52pm UTC](https://discuss.jsonapi.org/t/generic-relationships-linked-to-heterogeneous-resources/2480 "2022-07-26T22:52:47Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![bokara](https://avatars.discourse-cdn.com/v4/letter/b/ea5d25/32.png) [@bokara](https://discuss.jsonapi.org/u/bokara)
#### Post date: [July 28, 2022, 8:28pm UTC](https://discuss.jsonapi.org/t/generic-relationships-linked-to-heterogeneous-resources/2480/3 "2022-07-28T20:28:54Z")

</div>

thanks @fdrake , but was more about to see if can support a relationship path that’s beyond the filtered by type. i.e.,

instead of  
[http://www.example.com/debtors?filter[assets.type]=houses](http://www.example.com/debtors?filter%5Bassets.type%5D=houses)

trying to see if with a generic relationship (assets) that links to heterogeneous resource types (houses/cars/securities etc),

would it be possible to achieve something like this

> /debtors?included= **assets.houses** &filter[**assets.houses.zipcode**]=xxx

i.e.,  
with JSON:API spec, would that kind of relationship path be possible? or that would be implementation semantic?

---

_[View the full topic](https://discuss.jsonapi.org/t/generic-relationships-linked-to-heterogeneous-resources/2480)._