Issues
post/tasks/v1/incidents/submit

Request

  • Base URL
    https://api.mitti.com
  • Auth
    HTTP bearer

Request body

task_idstring

Optional. The unique identifier of the incident If not provided, UUID will be generated server side

titlestring required

Required. Title of the incident Title is limited to only 255 characters max

created_atstring date-time

Optional. Date and time this incident was created

category_idstring required

Required. ID of the incident's category If not set, this incident will be stored with the default category(None)

answered_questionsstring[]

Optional. An array of all, if any, custom questions that have been answered by the contributor @deprecated: Use QuestionAnswer instead. This was a field used for string custom questions. We've since moved to structured custom questions in the QuestionAnswer field.

emailstring

Optional. The email address of the contributor

site_idstring

Optional. ID of the site to associate with the incident. If not provided, no site will be associated with the incident.

namestring

Optional. The name of the contributor

contactstring

Optional. The contact details of the contributor

access_tokenstring

Optional. The access token used to authenticate the request. This field should be set when following the contributor flow. Otherwise, authenticate via normal means.

descriptionstring

Optional. Description of the issue (maximum 500 characters).

occurred_atstring date-time

Optional. Date and time this incident occurred at

asset_idstring

Optional. The ID of the asset associated with this incident.

ai_generatedboolean

Use ai_marking. True when this issue was created via an AI-assisted flow, for example the QR-code AI Issue Creation flow seeded by GenerateIncidentStream.

Response

A successful response.

incident_idstring

The UUID of the incident that was created.

unique_idstring

The unique id of the incident that was created. Formatted like: IS-1234.

Changes