Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
PhilippeG
Contributor
Contributor

NPrinting API POST method Create connection request --> http 400 - Bad Request - "Request is malformed."

Dear All,

I would need help in Creating a Connection in NPrinting using NPrinting API call from POSTMAN.

Given below are the steps I followed.

Before creating the request I got the correct App ID from NPrinting (GET /apps)

 

here the json in body and error received :

PhilippeG_0-1651657815546.png

Version :

PhilippeG_1-1651657882106.png

documentation :
https://help.qlik.com/en-US/nprinting/May2021/APIs/NP+API/index.html?page=23

Labels (2)
1 Solution

Accepted Solutions
PhilippeG
Contributor
Contributor
Author

hi Ruggero,

Thank you for your answer, but I had already checked all that.

in the meantime I found the cause of the problem:
the Content-Length box was not checked in the headers to send!

when I check Content-Length it works fine 🙂

PhilippeG_0-1651665803415.png

 

View solution in original post

2 Replies
Ruggero_Piccoli
Support
Support

Hi,

Please give a check at the article https://community.qlik.com/t5/Knowledge/How-to-Authenticate-Connect-with-the-Qlik-NPrinting-API-in/t... that covers the POST call via PostMan and let us know if it solves.

Best Regards,

Ruggero



Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
PhilippeG
Contributor
Contributor
Author

hi Ruggero,

Thank you for your answer, but I had already checked all that.

in the meantime I found the cause of the problem:
the Content-Length box was not checked in the headers to send!

when I check Content-Length it works fine 🙂

PhilippeG_0-1651665803415.png