Skip to main content
POST
Submit Ticket Feedback

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

ticket_id
string
required

The ID of the ticket the feedback is about.

Body

application/json
detailed
detailed · object
required
userId
string | null

The user giving the feedback. Defaults to the ticket's requester. If the ticket has a pending feedback request for this user it is answered; if the user already answered, the latest submission replaces their rating (an omitted text_feedback keeps the existing comment); otherwise a feedback record is created and answered in one step.

Response

200 - application/json

Success

data
data · object