AttachmentControllerApiAll URIs are relative to https://api.mailslurp.comMethodHTTP requestDescriptiondelete_all_attachmentsdelete /attachmentsDelete all attachmentsdelete_attachmentdelete /attachments/{attachmentId}Delete an attachmentdownload_attachment_as_base64_encodedget /attachments/{attachmentId}/base64Get email attachment as base64 encoded string as alternative to binary responses. To read the content decode the Base64 encoded contents.download_attachment_as_bytesget /attachments/{attachmentId}/bytesDownload attachments. Get email attachment bytes. If you have trouble with byte responses try the downloadAttachmentBase64 response endpoints.get_attachmentget /attachments/{attachmentId}Get an attachment entityget_attachment_infoget /attachments/{attachmentId}/metadataGet email attachment metadata informationget_attachmentsget /attachmentsGet email attachmentsupload_attachmentpost /attachmentsUpload an attachment for sending using base64 file encoding. Returns an array whose first element is the ID of the uploaded attachment.upload_attachment_bytespost /attachments/bytesUpload an attachment for sending using file byte stream input octet stream. Returns an array whose first element is the ID of the uploaded attachment.upload_multipart_formpost /attachments/multipartUpload an attachment for sending using a Multipart Form request. Returns an array whose first element is the ID of the uploaded attachment.delete_all_attachmentsdelete_all_attachments() Delete all attachmentsParametersThis endpoint does not need any parameter.Return type(empty response body)AuthorizationAPI_KEYHTTP request headersContent-Type: Not definedAccept: Not defined[Back to top] [Back to API list] [Back to Model list] [Back to ]delete_attachmentdelete_attachment(attachment_id) Delete an attachmentEmail attachments are essentially files with meta data. Files are byte arrays and the meta data is a content type and a filename. These properties allow email clients to display the filename and icon etc. When sending emails with attachments first upload each attachment with an upload endpoint. Record the returned attachment ID and use it with subsequent email sending. For legacy reasons the ID is returned as the first element in an array. Only a single ID is ever returned. To send the attachments pass a list of attachment IDs with SendEmailOptions when sending an email. Using the upload endpoints prior to sending mean attachments can easily be reused.ParametersNameTypeDescriptionRequiredNotesattachment_idStringID of attachment[required]Return type(empty response body)AuthorizationAPI_KEYHTTP request headersContent-Type: Not definedAccept: Not defined[Back to top] [Back to API list] [Back to Model list] [Back to ]download_attachment_as_base64_encodedcrate::models::DownloadAttachmentDto download_attachment_as_base64_encoded(attachment_id) Get email attachment as base64 encoded string as alternative to binary responses. To read the content decode the Base64 encoded contents.Returns the specified attachment for a given email as a base 64 encoded string. The response type is application/json. This method is similar to the downloadAttachment method but allows some clients to get around issues with binary responses.ParametersNameTypeDescriptionRequiredNotesattachment_idStringID of attachment[required]Return typecrate::models::DownloadAttachmentDtoAuthorizationAPI_KEYHTTP request headersContent-Type: Not definedAccept: application/json[Back to top] [Back to API list] [Back to Model list] [Back to ]download_attachment_as_bytesString download_attachment_as_bytes(attachment_id) Download attachments. Get email attachment bytes. If you have trouble with byte responses try the downloadAttachmentBase64 response endpoints.Returns the specified attachment for a given email as a stream / array of bytes. You can find attachment ids in email responses endpoint responses. The response type is application/octet-stream.ParametersNameTypeDescriptionRequiredNotesattachment_idStringID of attachment[required]Return typeStringAuthorizationAPI_KEYHTTP request headersContent-Type: Not definedAccept: application/octet-stream[Back to top] [Back to API list] [Back to Model list] [Back to ]get_attachmentcrate::models::AttachmentEntity get_attachment(attachment_id) Get an attachment entityEmail attachments are essentially files with meta data. Files are byte arrays and the meta data is a content type and a filename. These properties allow email clients to display the filename and icon etc. When sending emails with attachments first upload each attachment with an upload endpoint. Record the returned attachment ID and use it with subsequent email sending. For legacy reasons the ID is returned as the first element in an array. Only a single ID is ever returned. To send the attachments pass a list of attachment IDs with SendEmailOptions when sending an email. Using the upload endpoints prior to sending mean attachments can easily be reused.ParametersNameTypeDescriptionRequiredNotesattachment_idStringID of attachment[required]Return typecrate::models::AttachmentEntityAuthorizationAPI_KEYHTTP request headersContent-Type: Not definedAccept: application/json[Back to top] [Back to API list] [Back to Model list] [Back to ]get_attachment_infocrate::models::AttachmentMetaData get_attachment_info(attachment_id) Get email attachment metadata informationReturns the metadata for an attachment. It is saved separately to the content of the attachment. Contains properties name and content-type and content-length in bytes for a given attachment.ParametersNameTypeDescriptionRequiredNotesattachment_idStringID of attachment[required]Return typecrate::models::AttachmentMetaDataAuthorizationAPI_KEYHTTP request headersContent-Type: Not definedAccept: application/json[Back to top] [Back to API list] [Back to Model list] [Back to ]get_attachmentscrate::models::PageAttachmentEntity get_attachments(before, file_name_filter, page, since, size, sort) Get email attachmentsGet all attachments in paginated response. Each entity contains meta data for the attachment such as name and content-type. Use the attachmentId and the download endpoints to get the file contents.ParametersNameTypeDescriptionRequiredNotesbeforeOption<String>Filter by created at before the given timestampfile_name_filterOption<String>Optional file name and content type search filterpageOption<i32>Optional page event list pagination[default to 0]sinceOption<String>Filter by created at after the given timestampsizeOption<i32>Optional page size event list pagination[default to 20]sortOption<String>Optional createdAt sort direction ASC or DESC[default to ASC]Return typecrate::models::PageAttachmentEntityAuthorizationAPI_KEYHTTP request headersContent-Type: Not definedAccept: application/json[Back to top] [Back to API list] [Back to Model list] [Back to ]upload_attachmentVec upload_attachment(upload_options) Upload an attachment for sending using base64 file encoding. Returns an array whose first element is the ID of the uploaded attachment.Email attachments are essentially files with meta data. Files are byte arrays and the meta data is a content type and a filename. These properties allow email clients to display the filename and icon etc. When sending emails with attachments first upload each attachment with an upload endpoint. Record the returned attachment ID and use it with subsequent email sending. For legacy reasons the ID is returned as the first element in an array. Only a single ID is ever returned. To send the attachments pass a list of attachment IDs with SendEmailOptions when sending an email. Using the upload endpoints prior to sending mean attachments can easily be reused.ParametersNameTypeDescriptionRequiredNotesupload_optionsUploadAttachmentOptionsuploadOptions[required]Return typeVecAuthorizationAPI_KEYHTTP request headersContent-Type: application/jsonAccept: application/json[Back to top] [Back to API list] [Back to Model list] [Back to ]upload_attachment_bytesVec upload_attachment_bytes(content_type, filename, byte_array) Upload an attachment for sending using file byte stream input octet stream. Returns an array whose first element is the ID of the uploaded attachment.Email attachments are essentially files with meta data. Files are byte arrays and the meta data is a content type and a filename. These properties allow email clients to display the filename and icon etc. When sending emails with attachments first upload each attachment with an upload endpoint. Record the returned attachment ID and use it with subsequent email sending. For legacy reasons the ID is returned as the first element in an array. Only a single ID is ever returned. To send the attachments pass a list of attachment IDs with SendEmailOptions when sending an email. Using the upload endpoints prior to sending mean attachments can easily be reused.ParametersNameTypeDescriptionRequiredNotescontent_typeOption<String>Optional contentType for file. For instance application/pdffilenameOption<String>Optional filename to save upload withbyte_arrayOption<String>Byte array request bodyReturn typeVecAuthorizationAPI_KEYHTTP request headersContent-Type: application/octet-streamAccept: application/json[Back to top] [Back to API list] [Back to Model list] [Back to ]upload_multipart_formVec upload_multipart_form(file, content_type, filename, x_filename) Upload an attachment for sending using a Multipart Form request. Returns an array whose first element is the ID of the uploaded attachment.Email attachments are essentially files with meta data. Files are byte arrays and the meta data is a content type and a filename. These properties allow email clients to display the filename and icon etc. When sending emails with attachments first upload each attachment with an upload endpoint. Record the returned attachment ID and use it with subsequent email sending. For legacy reasons the ID is returned as the first element in an array. Only a single ID is ever returned. To send the attachments pass a list of attachment IDs with SendEmailOptions when sending an email. Using the upload endpoints prior to sending mean attachments can easily be reused.ParametersNameTypeDescriptionRequiredNotesfilestd::path::PathBuffile[required]content_typeOption<String>Optional content type of attachmentfilenameOption<String>Optional name of filex_filenameOption<String>Optional content type header of attachmentReturn typeVecAuthorizationAPI_KEYHTTP request headersContent-Type: multipart/form-dataAccept: application/json[Back to top] [Back to API list] [Back to Model list] [Back to ]