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). Copy Pagepost https://{account}.sysaidit.com/connect/v1/attachmentsCreate new attachmentBody ParamsCreation attachment metadataextensionstringrequiredAn Attachment extension (e.g. png, jpg).sourcestringrequiredlength between 1 and 20A source identifier (service_request).resourceIdintegerrequiredThe id of a resource, to which the attachment is added.resourceTypestringenumrequiredThe type of a resource, to which the attachment is added.SRTEMPLATEAI_CHATAI_DATASETAllowed:SRTEMPLATEAI_CHATAI_DATASETsubResourceIdintegerrequiredThe id of a subresource, to which the attachment is added.subResourceTypestringenumrequiredThe type of a subresource, to which the attachment is added.TEMPSRNOTEMESSAGESOLUTIONRESOLUTIONDESCRIPTIONAI_CHAT_MESSAGEAI_DATASET_RECShow 9 enum valuessizeInBytesintegerrequiredSize of the added attachment is bytes.checksumstringrequiredThe checksum that will be used for detecting an identical image in the same ticket of the same type.originalNamestringrequiredlength ≤ 50Attachment file name.visibilitybooleanDefaults to trueDefines whether the added attachment should be visible after creation.truefalsepathstringPath under which the attachment will be stored (e.g. on S3).generatedFileNamestringUnique attachment file identifier.Responses 200Attachment successfully created 400The request was invalid or cannot be served 401Authentication information is missing or invalidUpdated about 2 hours ago 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 GroupsDid this page help you?YesNo