# Proposal: Let's use "JPI" as the acronym to refer to JSON:API

**URL:** <https://discuss.jsonapi.org/t/proposal-lets-use-jpi-as-the-acronym-to-refer-to-json-api/1519>\
**Category:** Uncategorized\
**Created:** [February 14, 2019, 10:59pm UTC](https://discuss.jsonapi.org/t/proposal-lets-use-jpi-as-the-acronym-to-refer-to-json-api/1519 "2019-02-14T22:59:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ptolemy](https://avatars.discourse-cdn.com/v4/letter/p/b38774/32.png) [@Ptolemy](https://discuss.jsonapi.org/u/Ptolemy)\
**Post date:** [February 14, 2019, 10:59pm UTC](https://discuss.jsonapi.org/t/proposal-lets-use-jpi-as-the-acronym-to-refer-to-json-api/1519/1 "2019-02-14T22:59:50Z")

</div>

I recently read this really well thought out long-form article: [Headless CMS: REST vs JSON:API vs GraphQL](https://dri.es/headless-cms-rest-vs-jsonapi-vs-graphql). After reading it, I looked into JSON:API and found the spec to make a lot of logical sense to me. My understanding so far is that this spec provides a way to create public APIs that behave in a predictable and easy to understand way for clients while reducing the quantity of request-response cycles as much as possible.

Now, as a recent convert, I want to promote this spec to other software engineers I meet in my day-to-day life. One problem I am having for my evangelism is that JSON:API has a certain level of ambiguity to its name since many current REST APIs are JSON… APIs. In response to this confusion, I propose that we adopt an easy to say acronym that differentiates this spec more wholly from REST APIs and the best thing I could come up with is **JPI**.

Just sharing my thoughts on this matter since I would like to help this community grow.

---

<div class="post-metadata">

**Author:** ![maark](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.jsonapi.org/maark/32/184_2.png) [@maark](https://discuss.jsonapi.org/u/maark)\
**Post date:** [February 15, 2019, 12:43am UTC](https://discuss.jsonapi.org/t/proposal-lets-use-jpi-as-the-acronym-to-refer-to-json-api/1519/2 "2019-02-15T00:43:45Z")

</div>

I don’t have an opinion about _JPI_, but I do find the actual name **really** confusing. I’d like an acronym, nickname, or even a complete new name.

For example, sometimes people come on this board to ask questions about JSON APIs in general.