Rally Software

 View Only
  • 1.  Does Agile Central's next API version will be based GraphQL?

    Posted Feb 10, 2018 02:28 AM

    There are products already front facing GraphQL for their APIs.

     

    GitHub - APIs-guru/graphql-apis:    A collective list of public GraphQL APIs 

     

    Does CA Agile Central have any plans to expose its API in a form of GraphQL?



  • 2.  Re: Does Agile Central's next API version will be based GraphQL?

    Posted Feb 13, 2018 06:35 AM

    morky01 or corkr03 This one may be in your wheelhouse... 

     

    Michael



  • 3.  Re: Does Agile Central's next API version will be based GraphQL?

    Posted Feb 13, 2018 10:23 AM

    There aren't any plans at this time.  Are there specific problems with WSAPI that you think would be solved/made easier if we implemented a GraphQL API?



  • 4.  Re: Does Agile Central's next API version will be based GraphQL?

    Posted Feb 15, 2018 01:57 PM

    Yup,

     

    Of the three major problems, GraphQL solves, as an API consumer am facing the multiple HTTP calls to the server to get some particular data, average : 4 - 5 REST Calls to the Agile Central.



  • 5.  Re: Does Agile Central's next API version will be based GraphQL?

    Posted Feb 15, 2018 02:18 PM

    You can make multiple calls using the existing batch endpoint.  Unfortunately, this is not documented publicly yet, but you can use it today!  It's used for bulk edit/delete functionality in the product, but you can use it for issuing concurrent reads as well.

     

    Just do a POST to /slm/webservice/v2.0/batch with this payload format:

     

    {     Batch:  [         {             Entry: {                 Path: '/defect?fetch=Name&query=(Owner = /user/12345)',                 Method: 'GET'             }       },       {          Entry: {                 Path: '/hierarchicalrequirement?fetch=FormattedID',                 Method: 'GET'              }        },
           //additional entries...     ] }

     

    The above example shows querying defects and stories in one request.

     

    We've also discussed adding the sum/avg/count/(other aggregate operation) support into our fetch syntax.  I think this would be a great addition- hopefully I can explore this soon...