Why I dont see base64 element in the IDM API response?

Hi,

I see a lot of changes in IDM API without any intimation then what we had in 2020?

The response of IDM API ( items/search ) was base64 encoded string representing the physical document as an element in the XML response. Now I see document URL with the token instead? Why this change without intimation?

Is there any option to get the base64 format back? We are on MT Cloud

BR,

Niraj

Find more posts tagged with

ION API Gateway

Accepted answers

All comments

Brandon Watson

Hello Niraj! Unfortunately, I have never seen a Base64 document using GET, I have only seen it using PUT/POST, when submitting documents to IDM.

With that said, you could potentially build a data flow that gets the binary stream of the document, then pass that to a File Connection Point, as a binary document. You can then have another File Connection Point pickup the binary as a Sync.IDM_Stream_Binary, which will create an XML BOD with the binary base64 encoded "as-is".

Hopefully this helps!

Mats Ornvall

Hi,

I have used this kind of solution but one big issue with this is that you lose all other information you have in the BOD. You only get the binary as base64. I need to preserve information from the BOD.

Regards

Mats

Brandon Watson

I completely agree with you Mats! Looks like you are the one who put out the ERS for this. Maybe we can get more community members to vote for your ERS!

Enhancement Request - 66899 - IDM REST API to get the main resource as base64 (Like Stream but to base64) (infor.com)

Mats Ornvall

Yes,

I hope that people vote for ESR!

Can you use Octet-Stream in an APIflow? I guess you don't have an object type to put your reply back in to use in the next API. (I didn't manage that...)

Copyright © 2025 Infor. All rights reserved.