Managani Docs

Appearance

Toggle an authenticated or anonymous public feedback emoticon reaction ​

A valid signed user token takes precedence. Anonymous callers provide a stable site-scoped visitor ID and are not subscribed to feedback updates.

Request preparation ​

Send a POST request to /s/{slug}/feedback/{feedbackId}/reaction 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.
  • feedbackId (path, required): Use the type and constraints shown in the parameter reference.
  • X-User-Token (header, optional): Signed customer JWT with role admin or user
  • X-Managani-Visitor-ID (header, optional): Required when no valid signed user token is supplied.

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 ​

The specification lists these security alternatives: BearerAuth, AccessToken. Read any operation-specific restrictions as well: browser-session, account-role, and signed-user requirements may impose additional conditions. See authentication before choosing a credential.

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 Toggle an authenticated or anonymous public feedback emoticon reaction are:

  • 200: OK
  • 400: Valid signed user token or anonymous visitor ID required
  • 404: Feedback not found

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.

Toggle an authenticated or anonymous public feedback emoticon reaction​

POST
/s/{slug}/feedback/{feedbackId}/reaction

A valid signed user token takes precedence. Anonymous callers provide a stable site-scoped visitor ID and are not subscribed to feedback updates.

Authorizations​

BearerAuth

JWT token from login

Type
HTTP (bearer)
or
AccessToken

Personal access token. Value: Token <your-token>

Type
API Key (header: Authorization)

Parameters​

Header Parameters

X-User-Token

Signed customer JWT with role admin or user

Type
string
X-Managani-Visitor-ID

Required when no valid signed user token is supplied.

Type
string
Min Length
16
Max Length
200

Path Parameters

slug*
Type
string
Required
feedbackId*
Type
string
Required

Request Body​

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

Responses​

OK

Playground​

Authorization
Headers
Variables
Key
Value
Body

Samples​

Powered by VitePress OpenAPI