Confluence REST API: posting a comment needs a container object, not a bare ID

TL;DR

When posting a Confluence comment 500s on Must provide id and type for Content, fix the container field. Keep type as comment and the body in storage representation as before.

Steps

1. When posting a Confluence comment 500s on Must provide id and type for Content, fix the container field. It takes an object like id plus type page plus status current, not the bare page ID. Keep type as comment and the body in storage representation as before.

When to use

You are seeing this: It takes an object like id plus type page plus status current, not the bare page ID. Use this skill when you run into "Confluence REST API: posting a comment needs a container object, not a bare ID".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #28740312 (accepted answer, 4 votes): the asker POSTed a comment with container set to just the page ID and got a 500 Must provide id and type for Content. The accepted answer: container must be an object with id, type set to page, and status set to current.

Verified resolution: When posting a Confluence comment 500s on Must provide id and type for Content, fix the container field. It takes an object like id plus type page plus status current, not the bare page ID. Keep type as comment and the body in storage representation as before.

Source URL: https://stackoverflow.com/questions/28740312/how-do-you-post-a-comment-to-atlassian-confluence-using-their-rest-api