How to post with image or attachment

no reply?

Hi!

this is a bit confusing.. do you want to send a SOAP Request containing the file or simulate a HTML form submission containing the file?

regards!

/Ole
eviware.com

Exactly!

Hello,

The HTML you posted is a bit confusing. It seems it's an HTML form which contains a SOAP message and a file. Filling out this form and clicking on the submit button will not send a SOAP request, but rather an encoded HTML form containing the SOAP text and the file attachment. Are you trying to simulate the form submission which you posted the HTML for, or are you instead trying to send a SOAP request with a file attachment? Which of the two is it?

Regards,
Dain
eviware.com

Hi Suppport team,

Happy new year first!

Actually, our API is not a real SOAP.
It is a just a single HTTP request once using it.

I am wrapping the xml data in HTML form to send to the server.

Hello,

In this case, please see your other post regarding file attachments. You should be able to add them using the Attachments tab in the request. Good luck!

Regards,
Dain
eviware.com

Hi,

In the attached tab, I can upload the image but actually, it is not uploaded when i call the API.
I don't know how to attach the attachement.
that's why I am asking for your help........

Hi!

If you just want to upload an image make sure that you have set:
- the request to use either POST or PUT
- the "Media-Type" of the request to the same as the content-type of the attachment (as shown in the attachments table)

Does that help?

If not, can you attach a screenshot of how you have configured the request?

regards!

/Ole
eviware.com

Hi,

Please check my setting as attached.
It is called by POST method.
in the request raw:

POST http://api.kijiji.ca.staging.intern.qa- ... ApiCommand HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: multipart/form-data; boundary="----=_Part_47_15082019.1294634505798"
MIME-Version: 1.0
User-Agent: Jakarta Commons-HttpClient/3.1
Host: api.kijiji.ca.staging.intern.qa-kijiji.com
Content-Length: 87230


------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="xml"

<?xml version="1.0" encoding="UTF-8" ?> <SOAP:Envelope xmlns:SOAP="http://www.w3.org/2003/05/soap-envelope" > <SOAP:Body > </SOAP:Body> </SOAP:Envelope>
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Header/client/id"

1234
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Header/client/validation"

5566zgsc
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Header/command"

post
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Header/version"

1
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Body/user/email"

kijiji3@unicorn.qa.ebay.com
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Body/ad/area_id"

80002
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Body/ad/category_id"

103
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Body/ad/language_code"

1
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Body/ad/title"

API post private ad1
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Body/ad/description"

API post private ad1
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Body/ad/ask_price"

500
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Body/ad/address"

montreal
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Body/ad/format"

2
------=_Part_47_15082019.1294634505798
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: form-data; name="Body/image1"

file
------=_Part_47_15082019.1294634505798
Content-Type: application/octet-stream; name=file
Content-Transfer-Encoding: binary
Content-Disposition: form-data; name="file"; filename="file"
[a lot of non-printable chars here....]


The result is that, the attachment is not uploaded as the same as a single html call in the very beginning of the sample i gave.

according the solution of the other issue I post, I think it should be related to the ContentID setting as well.
Since in the HTML post way, its format is:
<input type = "file" name = "Body/image4" />

<input type = "submit" name = "submit" value = "submit" />

What the respect contentID for this?