-
Task
-
Resolution: Duplicate
-
Minor
-
None
-
None
-
None
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Engineering
-
-
3scale 2019-10-28, 3scale 2019-11-11, 3scale 2019-11-25
Now there is mix of output formats(xml and json) in outputs of calls of API functions in "3scale API Documentation". Some functions have xml output format and others json. I think it should be unified or user should have option to choose output format.
Dev notes
- We have XML for old APIs
- We must have JSON for all APIs
JSON is the way to go.
We might consider deprecating XML APIs later
We need to make sure that the swagger docs are updated accordingly and all the APIs have JSON equivalent to XML
We may have tests that only target the XML response. We need to make sure those are rewritten/extended to cover the JSON response as well.
- is related to
-
THREESCALE-5212 JSON API lists application plans with a different tag than XML API
- Closed
- relates to
-
THREESCALE-8993 CMS API - Fix JSON responses
- Closed
-
THREESCALE-529 upgrade the api docs definitions to swagger 2.0
- Closed
-
THREESCALE-5095 JSON API uses related resource links that are not JSON endpoints
- Closed
-
THREESCALE-5691 Review xml vs. json parameters in "3scale API Documentation"
- To Develop
-
THREESCALE-5715 Bring JSON API to level of XML API and possibly obsolete XML
- Closed