S7-1500 WebAPI - Error 400 BAD REQUEST

I am trying to test the WebAPI

I am using Tiaportal V17 upd 4, with an S7-1500 (6ES7 511-1AK02-0AB0 V2.9), and trying a POST request with Postman (https://www.postman.com/)

But I get error 400 (BAD REQUEST)

The S7-1500 webserver is working and I can login there as "admin"

I don't know what is wrong

If you manually send the json using CURL, does it work, or only when using a different tool?

Does the json webapi spec state POST or GET? 

I am assuming the PLC hardware configuration is allowing web requests and the PLC's security certificate is fully functional.

In the interim, I would (for testing purposes only) configure the plc to allow http requests, and then get the json to work with curl.  Once curl works, you can transition over to postman and https

AutoGen_5176452

Hello,

I am trying to test the WebAPI

I am using Tiaportal V17 upd 4, with an S7-1500 (6ES7 511-1AK02-0AB0 V2.9), and trying a POST request with Postman (https://www.postman.com/)

I am sending to "https://10.10.10.235/api/jsonrpc" this body:

{

   "jsonrpc":"2.0",

   "id":0,

   method:"Api.Login",

   params:  {user:"admin",

                    password:"admin"

                   } 

}

But I get error 400 (BAD REQUEST)

The S7-1500 webserver is working and I can login there as "admin"

I don't know what is wrong

0_Einstein

If you manually send the json using CURL, does it work, or only when using a different tool?

Does the json webapi spec state POST or GET? 

I am assuming the PLC hardware configuration is allowing web requests and the PLC's security certificate is fully functional.

In the interim, I would (for testing purposes only) configure the plc to allow http requests, and then get the json to work with curl.  Once curl works, you can transition over to postman and https

 With CURL in windows powershell I got this error

As far as I know, the webAPI only uses POST requests with jsonrpc

"I am assuming the PLC hardware configuration is allowing web requests and the PLC's security certificate is fully functional." How can I check this?

Using HTTP (previously admitting http conections on tia) gets error 400 BAD REQUEST:

Have you added the PLC security cert to the PC used for postman, curl and powershell?

As for the curl with http as a bad request, at least can you ping the plc at the defined ip address?  I am assuming you can based on the posts / replies so far.

Are you able to open the regular PLC web page at https://<plc ip> ?  How about http://<plc ip> ?

When you change hardware configuration, are you offline and then download to the plc forcing a PLC stop and restart before the changes take effect?

AutoGen_5176452

0_Einstein

If you manually send the json using CURL, does it work, or only when using a different tool?

Does the json webapi spec state POST or GET? 

I am assuming the PLC hardware configuration is allowing web requests and the PLC's security certificate is fully functional.

In the interim, I would (for testing purposes only) configure the plc to allow http requests, and then get the json to work with curl.  Once curl works, you can transition over to postman and https

 With CURL in windows powershell I got this error

As far as I know, the webAPI only uses POST requests with jsonrpc

"I am assuming the PLC hardware configuration is allowing web requests and the PLC's security certificate is fully functional." How can I check this?

Using HTTP (previously admitting http conections on tia) gets error 400 BAD REQUEST:

0_Einstein

Have you added the PLC security cert to the PC used for postman, curl and powershell?

As for the curl with http as a bad request, at least can you ping the plc at the defined ip address?  I am assuming you can based on the posts / replies so far.

Are you able to open the regular PLC web page at https://<plc ip> ?  How about http://<plc ip> ?

When you change hardware configuration, are you offline and then download to the plc forcing a PLC stop and restart before the changes take effect?

 I have this certificate (I don't know too much about certificates)

I can ping the PLC

I can enter with https

And with http

To load the program I am offline following this steps:

click on Load

Finish

Does this link help: https://support.industry.siemens.com/cs/document/68011496

or maybe this one which has example json for establishing & maintaining a connection and making api requests with json data: https://support.industry.siemens.com/cs/document/59193560

AutoGen_5176452

0_Einstein

Have you added the PLC security cert to the PC used for postman, curl and powershell?

As for the curl with http as a bad request, at least can you ping the plc at the defined ip address?  I am assuming you can based on the posts / replies so far.

Are you able to open the regular PLC web page at https://<plc ip> ?  How about http://<plc ip> ?

When you change hardware configuration, are you offline and then download to the plc forcing a PLC stop and restart before the changes take effect?

 I have this certificate (I don't know too much about certificates)

I can ping the PLC

I can enter with https

And with http

To load the program I am offline following this steps:

click on Load

Finish

Hi AutoGen_5176452,

Take a look at this (unofficial Siemens) video that might help you:

Siemens S7-1500 PLC JSON RPC Web API - Integrating Control Systems to Higher Level Systems with HTTP

Have you found the solution yet?

If not, have you set the Content-type: application/json and Content-length HTTP headers in your HTTP request? The webserver function manual gives an example on this.