Content

Operations

POST

Convert content ids to content types

Converts a list of content ids into their associated content types. This is useful for users migrating from v1 to v2 who may have stored just content ids without their associated type. This will return types as they should be used in v2. Notably, this will return inline-comment for inline comments and footer-comment for footer comments, which is distinct from them both being represented by comment in v1.

Permissions required: Permission to view the requested content. Any content that the user does not have permission to view or does not exist will map to null in the response.

Data Security Policy: Not exempt from app access rules

Scopes

OAuth 2.0 scopes required:

read:content.metadata:confluence

Connect app scope required: NONE

Request

Request bodyapplication/json

contentIds

array<anyOf [string, number]>

Required

Responses

Returned if the requested content ids are successfully converted to their content types

application/json

ContentIdToContentTypeResponse

POST/content/convert-ids-to-types

Forge

curl

Node.js

Java

Python

PHP

// This sample uses Atlassian Forge
// https://developer.atlassian.com/platform/forge/
import api, { route } from "@forge/api";

var bodyData = `{
  "contentIds": [
    "<string>"
  ]
}`;

const response = await api.asUser().requestConfluence(route`/wiki/api/v2/content/convert-ids-to-types`, {
  method: 'POST',
  headers: {
    'Accept': 'application/json',
    'Content-Type': 'application/json'
  },
  body: bodyData
});

console.log(`Response: ${response.status} ${response.statusText}`);
console.log(await response.json());

200Response

1
2
3

{
  "results": {}
}