My own REST gets HTTP 400 error in test client and it seems properly constructed.

Eric_Hohnbaum

I made my own REST api to test the process, but get an HTTP 400 Bad Request back from the Chrome Advanced REST Client.

Using the REST API Quick Start Guide as well as looking at a REST implementation in the ADN module, I created what looks like a properly registered REST implementation.

I orphaned RESTAPI:Root:RestAPI2 with a method Test1.  The fAction is "Test1', fResource is "atestmodule", fEnabled is true.

the Map object shows: {{'GET    | api/v2/atestmodule/test1','atestmodule | Test1'}}

And if you check the 

RESTAPI

you will see ,'atestmodule'=A<1,?,'test1'=A<1,?,'__PRIVATEMAP'='atestmodule|Test1','__PUBLICMAP'='GET|api/v2/atestmodule/test1'>>

so it seems properly registered.

 

In the test client, I use (PUT) otcs/cs.exe/api/v1/Auth to get a token, added to the header as OTCSTicket.  If I then change to GET and try v1/nodes/<someID> I get back results, but when I change the url to v2/atestmodule/Test1 I get the 400 Bad Request.  If I put a break point in RESTAPI:Root:RestAPI.Dispatch it never reaches it.

I tried it with the ADN Rest API and get the same 400 error. At first I assumed it was because the ADN functions require parameters, but my own Test1 requires none.

Screen shot of REST api testing.docx

Eric_Hohnbaum

I found the problem, I needed to set the content-type=application/x-www-form-urlencoded as well as set the OTCSTicket in the header.

When I changed the REST client from Post to Get, it lost that for some reason

So the two items in the Header Form are

content-type = application/x-www-form-urlencoded

OTCSTicket=<return from Auth call>