Skip to main content
POST
Move Ticket To Team

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.
  • Move between teams: Requires UPDATE_TICKET on both the source and destination teams. A key restricted to one team cannot move a ticket to another team.

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 to move. The owning (source) team is resolved server-side; callers do not (and must not) supply it.

Body

application/json
newTeamId
string

The ID of the team to move the ticket to.

Response

200 - application/json

Success

The response is of type MoveTicketToTeamResponse · object.