Finalize new attachment creation after the initial call to generate_presigned_url. The is the 3rd call made by the client in the creation flow (1st is generating a presigned URL, 2nd - uploading the object to storage using the presigned URL).

Create new attachment

Body Params

Creation attachment metadata

string
required

An Attachment extension (e.g. png, jpg).

string
required
length between 1 and 20

A source identifier (service_request).

integer
required

The id of a resource, to which the attachment is added.

string
enum
required

The type of a resource, to which the attachment is added.

Allowed:
integer
required

The id of a subresource, to which the attachment is added.

string
enum
required

The type of a subresource, to which the attachment is added.

integer
required

Size of the added attachment is bytes.

string
required

The checksum that will be used for detecting an identical image in the same ticket of the same type.

string
required
length ≤ 50

Attachment file name.

boolean
Defaults to true

Defines whether the added attachment should be visible after creation.

string

Path under which the attachment will be stored (e.g. on S3).

string

Unique attachment file identifier.

Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json