Has anyone managed to call the v3 multipart API using Python please ?

Hi everyone,

This is my first post here ...

I have followed the video tutorial and created the call in Postman and sent the parameter file and the Bod to the multipart gateway...

I have generated the Python code in postman.

I can retreive the token and ping the API, however I always get an empty body error when i send the parameter and payload files.

know there us code to do that in dot.net but find dot.net too complex.

ultimately, I am trying to created a recurssive pythong application to loop through a folder and make API calls to send BODs to ION.

1- I would appresiate a simple Pythong script to make a successful multopart API call.

2- Whats the best way to send bods to ION for integration with an ERP application that sends Json files (for example Purchase order bods).

3- if we are sending diffrent bods would the how would workflow handle diffrent bods comming through and fowrading then to Sun

Many thanks in advance for taking time to read my post.

Find more posts tagged with

ION API Gateway

Accepted answers

All comments

Kevin Heiman

Kind of a large subject ....

1. decision on best way to get data into a ION data flow

2. implementing Infor Messaging Service via Python.

There are several ways to get the data published to ION for a flow to process. Two of the common methods are; IMS API based and FTP or file based. Note that there are several other ways, I don't know your environment and options available to you.

assuming you want API based there is Infor Messaging service. This has a process requiring that you initiate a session, check for version, check to documents supported, then send the documents. All API best practices such as token expire/ refresh, jitter, retries, backoff should be implemented. https://docs.infor.com/inforos/2024.x/en-us/useradminlib_cloud/default.html?helpcontent=ioncedg_cloud_osm/mhn1519993806956.html

In the V3 version, a endpoint for /message/multipart was added in case you want something with a single file vs two.

I have a Python that uses the prior V3/multipartMessage endpoint.

Are you following the required sequence documented .. ping, protocol version, accepted documents , and what error do you get back?

Have been successful using testing in API gateway, collecting the CURL and testing in postman?

here is a excerpt of the multipart message ... assuming you have done all the other steps and monitor the error responses.

# We now have the bearer token for the duration of time "expires_in"

# set up api call headers with the Authorization for subsequent ION API calls

# boundary_value = "-----" + binascii.hexlify(os.urandom(16)).decode('ascii')

ionapiHeaders = {

'accept': 'application/json',

'Authorization': token["token_type"] + " " + token["access_token"],

'X-TenantId': ionapi["ti"],

# 'Content-Type': 'multipart/form-data'

}

<< APIs for preparing removed due to length. >>>>>

v3Multipart_URL = ionapi["iu"] + "/" + ionapi["ti"] +

"/IONSERVICES/api/ion/messaging/service/v3/multipartMessage"

v3Multipart_URL = v3Multipart_URL + "?logicalId=" + v3Multipart_logicalId

v3Multipart_URL = v3Multipart_URL + "&documentName=" + v3Multipart_documentName

# parameterFile is a string (or dict ) read in from file

# payloadFile is a string read in from file

payloadutf8 = payloadFile.encode("utf-8")

# build Multipart form data segment

# ION API CURL text:

# v3Multipart_Data = 'ParameterRequest=@CSL_SAP_Boomi_01_parameter_request'; +

# '.json;type=application/json' + '&' +

# 'MessagePayload=@CSL_SAP_Boomi_01_payload01'; +

# '.json;type=application/octet-stream'

IMS_payload = {}

IMS_files = [

('ParameterRequest', ('parameter',

open('%s' % (parameterFileLocation), 'rb'),

'application/json')),

('MessagePayload', ('payload',

open('%s' % (payloadFileLocation), 'rb'),

'application/octet-stream'))

]

# post data API call

try:

multipart_response = requests.request("POST", v3Multipart_URL,

headers=ionapiHeaders,

data=IMS_payload,

files=IMS_files)

# an async alternative : https://docs.aiohttp.org/

except requests.Timeout as error:

# Determine if a retry is needed

print(error)

# response from the api call

unknown

Hi Kevin,

Thanks a lot for your reply, what I am trying is to do is create an intergration between an ERP system and Sun.

I want a process to pickup the files from a folder and import them into SUN either using a python program picking files from a local folder or a share in AZURE or using ION to pick up files from an FTP site.

I see that you have commented out code and parts of the code that are either missing or unused like the lines.

Is it possible to send a clean code that works and acheive the sending of the file.

# payloadutf8 = payloadFile.encode("utf-8")

and

# boundary_value = "-----" + binascii.hexlify(os.urandom(16)).decode('ascii')

and

# v3Multipart_Data = 'ParameterRequest=@CSL_SAP_Boomi_01_parameter_request'; +
# '.json;type=application/json' + '&' +
# 'MessagePayload=@CSL_SAP_Boomi_01_payload01'; +
# '.json;type=application/octet-stream'

I am able to generate the token, the ping and the protocall calls, but not the multipart message call.

My code is the following:

-------------

from email.quoprimime import body_encode
from tokenize import Token
import requests
import pyodbc
import pandas as pd
import flatten_json as fjs
import json
import logging

logging.captureWarnings(True)

ci= "maskedvalue"
cn= "Postman_Backend_Service_Res_TST"
cs= "maskedvalue"
dt= "12"
ev= "V1532012214"
iu= "">mingle-ionapi.eu3.inforcloudsuite.com"
oa= "authorization.oauth2"
orev= "revoke_token.oauth2"
ot= "token.oauth2"
pu= "">mingle-sso.eu3.inforcloudsuite.com:443/.../"
saak= "maskedvalue"
sask= "maskedvalue"
ti= "maskedvalue"
v= "1.0"

ligicalid="lid://infor.ims.maskedvalue_ims_tst"
documentname="Vaximo_Test_KN"

baseurl="">mingle-ionapi.eu3.inforcloudsuite.com/.../service"
ping="/ping"
protocol="/protocol"
multipartmessage="/v3/multipartMessage?logicalId="+ligicalid+"&documentName="+documentname

url=pu+ot

pingurl=baseurl+ping
protocolurl=baseurl+protocol
multipartmessageurl=baseurl+multipartmessage

paramfilepath = 'C:\Users\Documents\work\PostMan_IMS_testing\ParamHeadersAS.json'
#print(f.read)

messagepayloadfilepath = 'C:\Users\Documents\work\PostMan_IMS_testing\MessagePayload'
#print(v.read)

authpayload = f"grant_type=password&client_id={ci}&client_secret={cs}&username={saak}&password={sask}"
authheaders = {"Authorization": "Bearer ACCESS_TOKEN_FROM_LAST_CURL", "accept": "application/json", "Config": "Live", "Content-Type":"application/x-www-form-urlencoded" }
response = requests.request("POST", url, data=authpayload, headers=authheaders)

response_data = response.json()
token = (response_data['access_token'])

df1=pd.json_normalize(response_data)
print (df1)

####protocol call

payload = {}
api_call_headers = {'Authorization': 'Bearer ' + token}
api_call_response = requests.get(protocolurl, headers=api_call_headers, verify=True)
api_call_response_data = api_call_response.json()
print("protocol response: ")
print(api_call_response_data)

####multipart call

test_api_url= multipartmessageurl
payload = { 'itemOne': str("test") }
paramfile=open(paramfilepath,'r')
paramfilecontent=paramfile.read()
#print(paramfilecontent)
messagepayload=open(messagepayloadfilepath,'rb')
messagepayloadcontent=messagepayload.read()
#print(messagepayloadcontent)

files=[
('ParameterRequest',('ParamHeaders.json',paramfilecontent,'application/json')),
('MessagePayload',('MessagePayload',messagepayloadcontent,'application/octet-stream'))
]
headers = {
'X-TenantId': 'maskedvalue',
'Content-Disposition':'form-data',
'Content-Type': 'multipart/form-data; '
'boundary=209964832652705914675009',
'Content-Lenght': '99',
'Transfert-Encoding': 'chunked',
'Accept': 'application/json',
'Authorization': 'Bearer ' + token}

req = requests.Request("POST", multipartmessageurl, headers=headers, data=payload, files=files)
r=req.prepare()
#print(r.body)
preparedbody = r.body.decode('utf8')
print(preparedbody)

s = requests.Session()
response=s.send(r)

#response = requests.request("POST", multipartmessageurl, headers=headers, data=payload, files=files,verify=False)

print("multipart response: ")
print(response.headers)
print(response.status_code)
print(response.text)
paramfile.close
messagepayload.close

-------------

Kevin Heiman

There is a lot to review in this.

I do not see the accepted documents being called. Do you have a an active endpoint for the logical ID specified, and is the document you are sending on that endpoint.?

I have to presume the header file is formatted correctly and accurate.

The Payload file is as mentioned in the documentation, a bin without suffix.

Message Payload File. The content type must be set to application/octet-stream. When selecting a file in this swagger, make sure that file has no extension, a '.bin' extension or any other extension which resolves to this content type.

Was it ZLIB compressed? compress Z_BEST_COMPRESSION or compressobj DEFLATED

There are a few spelling mistakes on the parameters that would invalidate them. I did not catch any that are required though, I might have missed.

I don't follow your code too well, and it has nothing to catch api fails / retries, but maybe that comes later.

The code I shared was all about the multipart message post. The commented lines were documentation, not to be hidden or uncommented.

You could also look at the API Gateway tracing to see more detail, but I suspect it is in the files you are posting, either content and compression. If you want to send the files in a zip to my email or my community inbox, I can try them in my environment.

unknown

Hi Kevin,

Yes agree the code has a lot of trouble shooting steps in it hence its not very clear to read, but executing it should be fine apart from the error we are getting.

Its replicating what we have in Postman.

In postman the payload file has no extention and so the file in the python script.

I have created an enpoint and a dataflow anything that is needed to send the bod to sun.

Will tray and find you email address and send you both files.

Many thanks for your time and help with this.

Much appreciated.

Copyright © 2025 Infor. All rights reserved.