Issues
FormDefinitions
Gets the full form definition with the specified ID.
Authentication
Requires Authorization header with valid Bearer token for scope issues:read.
For more documentation on authorization and how to get access token visit OAUTH2 Authorization page.
Request parameters
The ID of the form definition to get. This should be an ID retrieved from the "Get project form definitions" endpoint or an issue's "formId" property.
Request headers
OAuth access token with scope issues:read
Setting to application/vnd.bentley.itwin-platform.v1+json is recommended.
Response 401 Unauthorized
This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.
Response 404 Not Found
This response indicates that the form definition with the specified ID does not exist or is inaccessible to the user.
Response 429 Too many requests
This response indicates that the user has sent too many requests in a given amount of time.
The number of requests exceeds the rate-limit for the client subscription.
Form Definition Details
Unique identifier for this form definition. Can be set as the formId property in the 'Create issue' request body.
The name of this form definition as it should be displayed to users if they are choosing which form definition to use for a new issue.
Determines which issue type will be created when this form definition is used.
A JSON string defining this form's layout, including all of its controls and their bindings, locations, and styles. As of now third-party applications are not expected to use this property. An automated custom form renderer that works with this REST API is reserved for future development.
The form definition's availability. This can be set by a project administrator. Only forms set to Approved can be used to create issues. Possible values: 'Draft', 'Approved', 'Archived'.
String describing whether the form definition has problems that could prevent it from displaying (Warning) or functioning (Error or Critical) correctly. Possible values: 'None', 'Warning', 'Error', 'Critical', 'Unknown'.
error-response
Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.
Short string indicating the general category of error that occurred, such as '{Resource}NotFound'.
Longer string explaining to developers why the error occurred.
If relevant, this is the name of the property, URL template parameter, or query parameter that caused the error.
Error
Contains error information and an optional array of more specific errors.
One of a server-defined set of error codes.
A human-readable representation of the error.
The target of the error.
Error Details
Contains error information.
One of a server-defined set of error codes.
A human-readable representation of the error.
The target of the error.
Error Response
Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.