# Is it possible to discover types (e.g. via GET /)?

**URL:** <https://discuss.jsonapi.org/t/is-it-possible-to-discover-types-e-g-via-get/2509>\
**Category:** Uncategorized\
**Created:** [September 6, 2022, 10:38am UTC](https://discuss.jsonapi.org/t/is-it-possible-to-discover-types-e-g-via-get/2509 "2022-09-06T10:38:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![andi](https://avatars.discourse-cdn.com/v4/letter/a/5fc32e/32.png) [@andi](https://discuss.jsonapi.org/u/andi)\
**Post date:** [September 6, 2022, 10:38am UTC](https://discuss.jsonapi.org/t/is-it-possible-to-discover-types-e-g-via-get/2509/1 "2022-09-06T10:38:49Z")

</div>

Assume a generic client is just pointed to any JSON:API endpoint, i.e. is not familiar with the types and fields. Once you find a “starting point” like /articles, you can get resources, discover fields and related types and resources.

Is it possible to get a list of types? I’ve seen some discussions on adding this in the meta descriptions, but it does not seem to be a required part of the spec.

---

<div class="post-metadata">

**Author:** ![jelhan](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/jelhan/32/822_2.png) [@jelhan](https://discuss.jsonapi.org/u/jelhan)\
**Post date:** [November 16, 2022, 9:35pm UTC](https://discuss.jsonapi.org/t/is-it-possible-to-discover-types-e-g-via-get/2509/2 "2022-11-16T21:35:10Z")

</div>

This is not covered by the JSON:API specification itself. It could be standardized using an [extension](https://jsonapi.org/format/#extensions).