# NocoDB API Response Type Mismatch for OpenAPI

**URL:** <https://community.nocodb.com/t/nocodb-api-response-type-mismatch-for-openapi/2017>\
**Category:** APIs\
**Tags:** data-import-export\
**Created:** [July 23, 2025, 5:25pm UTC](https://community.nocodb.com/t/nocodb-api-response-type-mismatch-for-openapi/2017 "2025-07-23T17:25:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hitu-C](https://avatars.discourse-cdn.com/v4/letter/h/b9bd4f/32.png) [@Hitu-C](https://community.nocodb.com/u/Hitu-C)\
**Post date:** [July 23, 2025, 5:25pm UTC](https://community.nocodb.com/t/nocodb-api-response-type-mismatch-for-openapi/2017/1 "2025-07-23T17:25:30Z")

</div>

There is an inconsistency between the OpenAPI specification and the actual API response `Content-Type` for the link records endpoint: `https://app.nocodb.com/api/v2/tables/{tableId}/links/{linkFieldId}/records/{recordId}`.

The OpenAPI specification clearly defines that `200 OK` responses for the `GET`, `POST`, and `DELETE` operations on this path should return `Content-Type: application/json`. However, the API is currently returning `Content-Type: text/html` with a plain string body (e.g., “true” for `POST`/`DELETE`).

This mismatch causes issues for clients that strictly adhere to the OpenAPI specification for response deserialization. For example, our application, using a Rust OpenAPI client fails to deserialize the `text/html` response into the expected JSON structure.

Minimal cURL request (needs filled parameters of course):

```auto
curl -X POST 'https://app.nocodb.com/api/v2/tables/foo/links/bar/records/1234' -H 'xc-token: my_token' -H 'Content-Type: application/json' --data '{
  "Id": 5678
}'

```

---

<div class="post-metadata">

**Author:** ![Navi](https://avatars.discourse-cdn.com/v4/letter/n/3be4f8/32.png) [@Navi](https://community.nocodb.com/u/Navi)\
**Post date:** [July 23, 2025, 5:28pm UTC](https://community.nocodb.com/t/nocodb-api-response-type-mismatch-for-openapi/2017/2 "2025-07-23T17:28:27Z")

</div>

Have created an [issue internally](https://github.com/nocodb/nocohub/issues/6301)  
and we will be resolving this soon. Thank you for letting us know.

---

<div class="post-metadata">

**Author:** ![pranavxc](https://avatars.discourse-cdn.com/v4/letter/p/53a042/32.png) [@pranavxc](https://community.nocodb.com/u/pranavxc)\
**Post date:** [July 23, 2025, 5:47pm UTC](https://community.nocodb.com/t/nocodb-api-response-type-mismatch-for-openapi/2017/3 "2025-07-23T17:47:51Z")

</div>

Thanks for flagging this!

The behaviour you’re seeing is from our old API (v2). We’ve addressed these response inconsistencies in our new API v3, which provides standardised JSON responses across all endpoints, including links.

We recommend migrating to API v3 to avoid such issues and benefit from improved consistency and features.

You can find the v3 documentation here: [NocoDB API Documentation](https://nocodb.com/apis/v3/data#tag/Linked-Records)

* * *

_Note_: We will update the necessary changes on API v2 schema soon and rollout.