# Incorrect schema of REST response for endpoint /application/currentApplication/settings

**URL:** <https://community.cumulocity.com/t/incorrect-schema-of-rest-response-for-endpoint-application-currentapplication-settings/4073>\
**Category:** Forum\
**Tags:** cumulocity\
**Created:** [November 10, 2023, 12:18pm UTC](https://community.cumulocity.com/t/incorrect-schema-of-rest-response-for-endpoint-application-currentapplication-settings/4073 "2023-11-10T12:18:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniel.steiner](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/daniel.steiner/32/32072_2.png) [@daniel.steiner](https://community.cumulocity.com/u/daniel.steiner)\
**Post date:** [November 10, 2023, 12:18pm UTC](https://community.cumulocity.com/t/incorrect-schema-of-rest-response-for-endpoint-application-currentapplication-settings/4073/1 "2023-11-10T12:18:14Z")

</div>

#### _ **Product/components** used and **version/fix** level:_

1017.0.289 (Production use)

#### _Detailed explanation of the problem:_

When working with the OpenAPI specification for Cumulocity and noticed that when querying the endpoint **{{baseUrl}}/application/currentApplication/settings** (using a bootstrap user) the resulting response is not compliant with the schema provided in the specification (see [Cumulocity - OpenAPI](https://cumulocity.com/api/core/#operation/getCurrentApplicationResourceSettings)).

Therefore when sending the **Accept** header with value **application/vnd.com.nsn.cumulocity.applicationsettings+json** (as shown in the spec) the response status is **406 - Not Acceptable** without a response body. When omitting the the header i receive a response **200 - OK** with a response body, but not in the format given in the specification, instead the result is just returned as a “key - value” list for each setting.

This does occur in a microservice context as well as when using postman. Is this just an issue with our deployed version/fix-version or a general problem?

#### _Error messages / **full error** message screenshot / **log** file:_

Relevant section of the openapi spec:

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/cumulocity/original/3X/7/9/797f4d65c6ab3fd92615384de6370129d00ea299.png)

Response in postman when sending accept header:

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/cumulocity/original/3X/a/f/afd8b44b6c015e86c3a804787ab8533bc78eeecf.png)

Response when not sending accept header:

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/cumulocity/original/3X/6/e/6e06f3c73c9eb0e85053b01f933c749ffb20a134.png)

---

<div class="post-metadata">

**Author:** ![Harald\_Meyer](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/harald_meyer/32/1959_2.png) [@Harald\_Meyer](https://community.cumulocity.com/u/Harald_Meyer)\
**Post date:** [November 13, 2023, 6:28am UTC](https://community.cumulocity.com/t/incorrect-schema-of-rest-response-for-endpoint-application-currentapplication-settings/4073/2 "2023-11-13T06:28:09Z")

</div>

What is the actual content type of the response? Is it application/vnd.com.nsn.cumulocity.option+json? What happens if you use that in your ACCEPT header?

To me this looks like an error in the OpenAPI specification.

---

<div class="post-metadata">

**Author:** ![daniel.steiner](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/daniel.steiner/32/32072_2.png) [@daniel.steiner](https://community.cumulocity.com/u/daniel.steiner)\
**Post date:** [November 13, 2023, 12:18pm UTC](https://community.cumulocity.com/t/incorrect-schema-of-rest-response-for-endpoint-application-currentapplication-settings/4073/3 "2023-11-13T12:18:21Z")

</div>

Hi,

> To me this looks like an error in the OpenAPI specification.

Yes that was kind of what i was implying, the actual content type returned by the request is **application/vnd.com.nsn.cumulocity.option+json;charset=UTF-8;ver=0.9** , the request works fine when using this content type. Since we are working off the OpenAPI specification this just popped up as inconsitency.

Should i contact our SAG support team with this issue, or is there some other place where this can be reported?

---

<div class="post-metadata">

**Author:** ![Harald\_Meyer](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/harald_meyer/32/1959_2.png) [@Harald\_Meyer](https://community.cumulocity.com/u/Harald_Meyer)\
**Post date:** [November 13, 2023, 12:36pm UTC](https://community.cumulocity.com/t/incorrect-schema-of-rest-response-for-endpoint-application-currentapplication-settings/4073/4 "2023-11-13T12:36:03Z")

</div>

For documentation issues, you report them directly from the documentation by clicking on the Bugherd button in the lower-right hand corner of the page (button is only shown if Adblocker is disabled on page):

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/cumulocity/original/3X/a/7/a755ce4feb28e7877a8ad90c8ee341d69a3473aa.png)

Alternatively, you can also create a support ticket but the maintainer of the OpenAPI specification is aware of the problem already anyway.

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/system/32/31990_2.png) [@system](https://community.cumulocity.com/u/system)\
**Post date:** [May 11, 2024, 12:36pm UTC](https://community.cumulocity.com/t/incorrect-schema-of-rest-response-for-endpoint-application-currentapplication-settings/4073/5 "2024-05-11T12:36:09Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.
