Managani Docs

Appearance

Edit an owned discussion comment ​

Signed project-user token required. Only the original external author can mutate a public/widget comment. Tenant, project, parent record, and comment scopes are checked. Eligible discussion changes sync to GitHub; internal notes and automatic AI comments remain local.

Request preparation ​

Send a PATCH request to /s/{slug}/discussion/{kind}/{recordId}/comments/{commentId} on the appropriate server. Check the API overview for base URL guidance and the server information in the interactive reference. Replace path placeholders with identifiers from the intended account or site; a similarly named record in another workspace is not interchangeable.

The declared request parameters are:

  • slug (path, required): Use the type and constraints shown in the parameter reference.
  • kind (path, required): Use the type and constraints shown in the parameter reference.
  • recordId (path, required): Use the type and constraints shown in the parameter reference.
  • commentId (path, required): Use the type and constraints shown in the parameter reference.
  • Authorization (header, required): Bearer signed project-user JWT

This operation defines a required request body. Documented media types: application/json. Review required fields, nested objects, and allowed values in the request schema. Keep identifiers and field types intact when replacing example data with your own values.

Authentication and scope ​

This operation does not declare an OpenAPI security requirement. Check the description and parameter definitions for any signed URL, customer identity, webhook, or browser-session conditions before using it outside a test environment.

Keep credentials in the appropriate private configuration and remove secrets from shared logs. Confirm the target resource belongs to the intended workflow before issuing a request. Authentication alone should not be treated as confirmation that a supplied account, site, or customer identifier is correct.

Response handling ​

The documented responses for Edit an owned discussion comment are:

  • 200: Updated or deleted owned comment
  • 401: Signed user required
  • 403: Comment belongs to another author
  • 404: Comment not found in project and parent scope

Exercise this operation with controlled test data before enabling it in an automated workflow. Validate the request against the schema and inspect the response before updating local state. Do not assume that a successful response means background processing has finished; follow any documented status or follow-up operation when the action queues additional work.

If a connection fails after submission, investigate the current server state before repeating an action whose outcome is uncertain. When requesting support, retain the method, route, response status, and sanitized error message. The interactive reference below provides the detailed schemas and examples for this specific operation.

Edit an owned discussion comment​

PATCH
/s/{slug}/discussion/{kind}/{recordId}/comments/{commentId}

Signed project-user token required. Only the original external author can mutate a public/widget comment. Tenant, project, parent record, and comment scopes are checked. Eligible discussion changes sync to GitHub; internal notes and automatic AI comments remain local.

Parameters​

Header Parameters

Authorization*

Bearer signed project-user JWT

Type
string
Required

Path Parameters

slug*
Type
string
Required
kind*
Type
string
Required
Valid values
"feedback""release"
recordId*
Type
string
Required
commentId*
Type
string
Required

Request Body​

application/json
JSON
{
  
"body": "string"
}

Responses​

Updated or deleted owned comment

Playground​

Headers
Variables
Key
Value
Body

Samples​

Powered by VitePress OpenAPI