We are integrating the Genesys Cloud Web Messaging Guest API into our custom portal to allow customers to submit support tickets with attachments. The requirement is strict regarding data integrity. We need to enforce specific MIME types and file size limits before initiating the upload process via the API.
The current implementation uses a direct POST request to /api/v2/conversations/messaging/messages with a multipart/form-data payload. The code snippet below illustrates the request structure we are using in our Node.js backend service.
const axios = require('axios');
async function uploadAttachment(conversationId, fileBuffer, fileName, mimeType) {
const formData = new FormData();
formData.append('file', fileBuffer, {
filename: fileName,
contentType: mimeType
});
try {
const response = await axios.post(
`https://api.mypurecloud.com/api/v2/conversations/messaging/messages/${conversationId}/attachments`,
formData,
{
headers: {
...formData.getHeaders(),
'Authorization': `Bearer ${authToken}`,
'Content-Type': 'multipart/form-data'
}
}
);
return response.data;
} catch (error) {
console.error('Upload failed:', error.response.status, error.response.data);
throw error;
}
}
The issue arises when the client sends a file with a MIME type that is technically valid but not supported by Genesys Cloud for messaging attachments, such as application/x-executable or certain archive formats. The API returns a 400 Bad Request with a generic error message that does not specify the exact constraint violation. We want to validate these constraints on our side to provide a better user experience.
The documentation mentions size limits but does not provide a full list of accepted MIME types or the exact byte limit for attachments in Web Messaging conversations. We are currently guessing a 5MB limit based on general guidelines, but this is not confirmed.
Has anyone successfully implemented client-side validation for these constraints? We are looking for the definitive list of allowed MIME types and the exact maximum file size allowed for the Guest API upload endpoint. We need to ensure our validation logic matches the platform’s internal checks to avoid unnecessary API calls and failed uploads.