Skip to main content
POST
Create Improvement Request

Authentication and permissions

Token requirements: User-based token (OAuth). 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. Only a signed-in user can file an improvement request; API keys are refused.
  • New ticket: Without ticket_id, opens a ticket on team_id that holds the request, with you as its requester.
  • Attach to a team ticket: With ticket_id, the ticket must be visible to you.
  • Attach to your own ticket: With ticket_id, you must be the ticket’s requester. Not available for system-created tickets or tickets restricted to their team.

Authorizations

Authorization
string
header
required

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

Body

application/json
teamId
string | null

The ID of the team to ask. Required unless ticket_id is set; a new ticket is opened on this team.

ticketId
string | null

Optional. The ID of an existing ticket to attach the request to. When omitted, a new ticket is opened on team_id to hold the request.

description
string

What should improve: the recurring need, and what a good outcome looks like. It becomes the body of the message the request is attached to.

Response

200 - application/json

Success

data
data · object

A requester's ask for the team to improve how a kind of request is handled: a workflow, a Help Desk Skill, a knowledge change, or a mix. It is attached to the ticket message it was filed in, whose body is its description.