# OpenAPI 3.0 spec that conforms to JSON:API

**URL:** <https://discuss.jsonapi.org/t/openapi-3-0-spec-that-conforms-to-json-api/1803>\
**Category:** Uncategorized\
**Created:** [January 7, 2020, 6:26pm UTC](https://discuss.jsonapi.org/t/openapi-3-0-spec-that-conforms-to-json-api/1803 "2020-01-07T18:26:20Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [January 9, 2020, 4:46pm UTC](https://discuss.jsonapi.org/t/openapi-3-0-spec-that-conforms-to-json-api/1803/4 "2020-01-09T16:46:37Z")

</div>

Is OpenAPI 3 a requirement, or are alternatives an option for you? I worked with RAML 1.0 for a while, and it was much more expressive than OpenAPI 3.

That said, the _tooling_ available for RAML 1.0 wasn’t that great, and I ended up switching to OpenAPI 3 for better documentation generation. (I’m not currently using any tooling for code or test generation, or other runtime support; the specifications are just documentation at this point.)

All of that was before I started looking at JSON:API, though.

---

_[View the full topic](https://discuss.jsonapi.org/t/openapi-3-0-spec-that-conforms-to-json-api/1803)._