> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.itential.com/itential-platform/6/release-notes/deprecations/reduced-integration-responses/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server.

# Reduced integration responses

> Notice that the dual-format integration response is deprecated in Platform 6 and replaced with a single response format determined by the Content-Type HTTP header in Platform 6.1.

## Deprecation notice

The following deprecation has been issued in the Itential Platform 6 release, with the change scheduled for the Platform 6.1 version.

### Dual-format response no longer supported

Integrations in prior Platform versions supplied response data in two formats: JSON and plain text. This dual-format response was inefficient as it doubled the amount of data flowing through the system, impacting performance and resource usage.

Beginning with the Platform 6.1 release, integrations will supply a single response format, as determined by the `Content-Type` HTTP header:

* If the `Content-Type` is set to `application/json`, integrations will automatically parse and return the response as JSON.
* For any other `Content-Type`, the response will default to plain text.

These changes will improve system efficiency, reduce overhead, and maintain flexibility by allowing you to specify an integration response format through standard HTTP headers. The integration response size will also be smaller, reducing impact on job execution performance.

### What should I do?

To prepare for this change, Itential recommends refactoring workflows to use the `"body"` response field within integration responses. This ensures the response is parsed correctly based on the `Content-Type` header. For example, if the `Content-Type` header is `"content-type": "application/xml"`, the `"body"` field will be formatted as text.

A sample response is shown below:

```json
{
  "response": {
    "ok": true,
    "url": "https://petstore.swagger.io/v2/pet/findByStatus?status=pending",
    "status": 200,
    "statusText": "OK",
    "headers": {
      "access-control-allow-headers": [
        "Content-Type",
        "api_key",
        "Authorization"
      ],
      "access-control-allow-methods": [
        "GET",
        "POST",
        "DELETE",
        "PUT"
      ],
      "access-control-allow-origin": "*",
      "connection": "keep-alive",
      "content-type": "application/json",
      "date": [
        "Thu",
        "30 Jan 2025 15:13:50 GMT"
      ],
      "server": "Jetty(9.2.9.v20150224)",
      "transfer-encoding": "chunked"
    },
    "body": [
      {
        "id": 31662904,
        "category": {
          "id": -72976378,
          "name": "consequat commodo dolor"
        },
        "name": "doggie",
        "photoUrls": [
          "dolor",
          "aliquip"
        ],
        "tags": [
          {
            "id": -81536039,
            "name": "officia non exercitation laborum"
          },
          {
            "id": -81700539,
            "name": "sed quis"
          }
        ],
        "status": "pending"
      },
      {
        "id": 31759937,
        "category": {
          "id": 1,
          "name": "Dogs"
        },
        "name": "Gordinho",
        "photoUrls": [
          "https://www.iamurl.com/labrador_gordinho.jpg"
        ],
        "tags": [
          {
            "id": 1,
            "name": "friendly"
          }
        ],
        "status": "pending"
      },
      {
        "id": 22292890,
        "category": {
          "id": 1,
          "name": "Dogs"
        },
        "name": "Gordinho",
        "photoUrls": [
          "https://www.iamurl.com/labrador_gordinho.jpg"
        ],
        "tags": [
          {
            "id": 1,
            "name": "friendly"
          }
        ],
        "status": "pending"
      },
      {
        "id": 24507780,
        "category": {
          "id": 1,
          "name": "Dogs"
        },
        "name": "Gordinho",
        "photoUrls": [
          "https://www.iamurl.com/labrador_gordinho.jpg"
        ],
        "tags": [
          {
            "id": 1,
            "name": "friendly"
          }
        ],
        "status": "pending"
      },
      {
        "id": 18774350,
        "category": {
          "id": 1,
          "name": "Dogs"
        },
        "name": "Gordinho",
        "photoUrls": [
          "https://www.iamurl.com/labrador_gordinho.jpg"
        ],
        "tags": [
          {
            "id": 1,
            "name": "friendly"
          }
        ],
        "status": "pending"
      }
    ],
    "method": "GET"
  }
}
```

If you experience any issues with refactoring or need additional assistance, contact the [Product Support Team](https://itential.atlassian.net/servicedesk/customer/portals).

### Related reading

* Removing duplicate data properties in response object

> Notice that the dual-format integration response is deprecated in Platform 6 and replaced with a single response format determined by the Content-Type HTTP header in Platform 6.1.