Ticket API
Create Status
Create a ticket status for a team.
POST
Create Status
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.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
application/json
Required. The status pool this status belongs to (e.g. TICKET_TYPE_REQUEST). There is no shared/default pool, so TICKET_TYPE_UNSPECIFIED is rejected.
Available options:
TICKET_TYPE_UNSPECIFIED, TICKET_TYPE_REQUEST, TICKET_TYPE_TASK, TICKET_TYPE_MAJOR_INCIDENT, TICKET_TYPE_CONVERSATION, TICKET_TYPE_JOURNEY, TICKET_TYPE_INCIDENT, TICKET_TYPE_CHANGE, TICKET_TYPE_CUSTOM, TICKET_TYPE_PROBLEM Available options:
TICKET_STATUS_GROUP_UNSPECIFIED, TODO, IN_PROGRESS, DONE, CANCELED The team-portable identity of the status. Omit to mint a new one; set it to preserve identity across teams (used by config push / Resource Manager).
Response
200 - application/json
Success

