Customer conversations can include both file attachments and recordings, depending on the channels that you use. With our files API, you are able to request and download all of these files, for storing or GDPR compliance purposes. How to retrieve attachments and call recordingsIf a customer conversation has any file attachment, you will be able to find a link to these when requesting the message endpoint of our Dixa API under attributes.The webhook event CONVERSATION_MESSAGE_ADDED also contains links to the file attachments.There are three different types of links:a) https://files.dixa.io/private/...b) /private/...c) /public/...In case a), the URL can be left as it is. For case b) and c), you need to add the domain and protocol as a prefix (https://files.dixa.io), so the URL becomes https://files.dixa.io/private/...If you follow the link to the respective file, you are redirected to our files API.Bulk attachments / call recordingsIf you need call recordings or attachments in bulk, take a look at our Message Export API, which contains the links to the call recordings and also includes attachments. Authentication to the files works the same way for both recordings and attachments, and is as described below.AuthorizationFor security, you'll need to authenticate your request with an authorization header if the path includes "private". For "public" attachments, no authentication is required. For "private" file authentication, use the API token, as a Basic authorization header. Use "bearer" as username, and your API token as password. Don't forget to base64 encode the username and password. Example header (replace yourapitoken with an API token):Authorization: Basic base64(bearer:yourapitoken) which would result in Authorization: BasicYmVhcmVyOnlvdXJhcGl0b2tlbg==Using this authorization header, you can make a GET request to the attachment or recording URL and you should get the requested file.Example request:curl -X GET -H "Authorization: Basic YmVhcmVyOnlvdXJhcGl0b2tlbg==" "https://files.dixa.io/private/....."