v1

latestOpenAPI 3.1.02026-07-2489171167.4 KB
Attachments

Generates a presigned url for an attachment upload

The 1st step in the new attachment creation flow - a request to generate a presigned URL that the client can use to upload an attachment

post/attachments/presigned-url

Request body

extensionstring required

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

sourcestring required

A source identifier (service_request)

resourceIdinteger required

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

resourceType'SR' | 'TEMPLATE' | 'AI_CHAT' | 'AI_DATASET' required

The resource type tells to which resource the attachment is attached to. All SR types are mapped to SR.

subResourceIdinteger required

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

subResourceType'TEMP' | 'SR' | 'NOTE' | 'MESSAGE' | 'SOLUTION' | 'RESOLUTION' | 'DESCRIPTION' | 'AI_CHAT_MESSAGE' | 'AI_DATASET_REC' required
sizeInBytesinteger required

Size of the added attachment is bytes

checksumstring required

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

Response

Attachment presigned url is successfully generated

pathstring

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

generatedFileNamestring

Unique attachment file identifier

presignedUrlstring uri required

A URL using which an attachment can be uploaded to the storage by a client