DevTest API Response Only Returning XML

[Anon Anon]

Hello,

 

I'm trying to call the DevTest API and I am able to do so, BUT I can only ever get the response as xml - even when using the DevTest Swagger UI and selecting the json content type. Can anybody provide any insight? I am making the call as follows:

 

 

 

 

 

      $.ajax({

                type: 'GET',              
                dataType: "json",
                contentType: "application/vnd.ca.lisainvoke.vse+json; charset=utf-8",
                url: 'http://' + server + ':1505/api/Dcm/VSEs/VSE',
                headers: {
                    'Authorization': "Basic " + btoa("username" + ':' + "password")
                }              
            })

 

 

 

 

[sdetweil1.1]

you would need to add the JSON DPH to convert the XML back to JSON on output..

the fact that you used swagger is lost after input

[Anon Anon]

correct me if i'm wrong, but it seems like you are talking about when creating virtual services or when recording.... I am talking about using DevTest's own API for metrics and reporting.

 

 

Im not sure why i would need to configure something additional when from the documentation it seems to be supported natiively.

[sdetweil1.1]

sorry, I didn't get that you were calling the invoke api

 

I posted some examples using curl a while back, not using ajax..

[Lenn Thompson]

Did Sam's guidance help you? Did you figure things out?

[Anon Anon]

Hi Lenn,

 

No, I have still not been able to get the data as json, instead I am getting the devtest api response as xml and then converting to json in my ETL process.

[Anon Anon]

I have just figured this out and it's spectacularly bad design on their part.

 

The Accepts header that you're meant to pass differs depending on which part of the REST API you're invoking. For example, the two commands below both work:

 

curl -H Accept:application/vnd.ca.lisaInvoke.vseList+json -u USERNAME:PASSWORD "http://LISAHOST/api/Dcm/VSEs"

curl -H Accept:application/vnd.ca.lisainvoke.VirtualService+json -u USERNAME:PASSWORD "http://LISAHOST/api/Dcm/VSEs/VSE4/serviceName"

 

Notice the bits in bold - the Accept header is different in each case. Funnily enough, that's what the root element in the response is called, vseList and VirtualService respectively (that's how I figured it out).

 

Why on earth it's not just accepting "application/json" is beyond me.