The API returns an empty message body when the message is long
I convert images to base64. When someone posts a message with 2+ large images, the message displays correctly in SuperOffice. However, the REST API returns the message with no value for both ‘body’ and ‘htmlbody'. Is the character limit lower for loading messages with the REST API then the character limit for posting messages?
All Replies (7)
Hi Vidar,
Please provide an example to reproduce:
1. What you expect
2. What you observe
Assuming you are just using the Ticket endpoint, and expecting to get back all properties of each ticket message...
Have you tried using the TicketMessage endpoint to get each individual message with body content?
Best regards.
Ticket, ticket/id/messages, ticketmessage, archive/dynamic - Same result.
In SuperOffice the message(created with REST API) has images:
What the API returns for the same message:
What the API returns for a message with just one small image:
Hi Vidar,
I am unable to recreate your observered error.
I did POST a ticketmessage with a 4.3MB image as base64 img source and it does appear successfully in the client, as you successfully observed as well.
When sending a GET request for that TicketMessage, I find that different clients handling the response differently. For example, using VS Code and the Rest Client extension with .http file, I observe this response:
And again with VS Code, using the ThunderBird extension (Similar to Postman), I initially observe this response:
Then, when I click the Open in Code link, the complete raw response is displayed containing the complete HtmlBody content with the entire base64 image string.
So, my question to you is, is it possible that the Postman client is truncating the base64 image string, and not the actual response?
Best regards.
Thank you for your reply. The size of the response and the raw result in postman is consistent with what I showed it the last reply. Thunder Client in VS code and HttpClient in c# gets the same result. (When testing, for example, the archive/dynamic endpoint I have reviced much larger responses)
Is there no known reason for why the REST API retruns a message diffrent from the message shown in SuperOffice?
Hi Vidar,
I can't confirm is this issue is related to Bug ID: 34693, but there was some issues with TicketMessage that was fixed in 10.1.8.
Best regards.