Comment on a resource
/org-content/resource/{resource_id}/commentsAdds a comment as the acting user and returns it with a Location. content is required, up to 150 characters; parent_id answers a live comment on the same resource; any other parent_id is dropped and the comment is written top-level. user_id, author or author_id returns 422 missing. dry_run shows the result without saving it. Emits org_content_comment.created; no email or notification. DELETE /org-content/comments/{id} undoes it.
Path parameters
The resource's id.
Query parameters
Validate and run the call without committing it, returning what the real call would return with
meta.dry_runset.
Headers
Makes a retry safe. Send a new UUID for each new request and reuse it only to retry that request; the first response is replayed for 24 hours.
Request body
application/json, required · OrgContentCommentCreate
The comment text, up to 150 characters.
The id of the comment this one answers, on the same item. Omit or null for a top-level comment.
{
"content": "Looking forward to this."
}Responses
{
"data": {
"id": 1,
"parent_id": 1,
"content": "string",
"author": {
"user_id": "9a9d1c5e-4f2b-4c8e-9a7d-2f1e6b3c4d5a",
"name": "string",
"organisation_id": "9a9d1c5e-4f2b-4c8e-9a7d-2f1e6b3c4d5a"
},
"created_at": "2026-06-12T10:00:00+00:00",
"updated_at": "2026-06-12T10:00:00+00:00"
}
}Authorization failed. error.code is one of org_disabled,
ip_blocked, missing_scope, scope_disabled, user_disabled.
The request can't be processed (HTTP 422): validation_failed with one ErrorDetail per
problem, or a code documented on the operation.
Examples
curl -X POST https://your-org-domain/kong/core/api/v2/org-content/resource/{resource_id}/comments\
-H "Authorization: Bearer $HELM_API_KEY"\
-H "Content-Type: application/json"\
-d '{
"content": "Looking forward to this."
}'