Skip to main content
POST
Open Team Form

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. Workspace keys must allow every workspace checked by the request. OAuth access depends on the user’s roles and resource access. Only a signed-in user can open or submit a team form; API keys are refused.
  • Team form: The form must be listed in team_id’s service catalog and available to you. Submitting creates a ticket on team_id with you as its requester.

Authorizations

Authorization
string
header
required

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

Body

application/json
teamId
string
formId
string

A service catalog form id, as listed in the team's resources.

values
values · object

Pre-filled answers keyed by field key. Values the form rejects are reported as field errors rather than failing the open.

Response

200 - application/json

Success

data
data · object