How to grab all the issues inside a jira structureboard using REST api - rest

I have been researching Jira REST api in order to grab all the test cases inside my structures but I haven't had any luck. The closes I have been to getting inside a structure is using the URL $baseUrl/rest/structure/2.0/structure. From there I tried to manipulate the url into giving me all the information about a specific structure.
For example, I used $baseUrl/rest/structure/2.0/structure/$id but I only got back
{"id":135,"name":"TEST PLAN 1","description":""}
There is hardly any information in this REST api call. IS there a way to have it list out all the issue keys(test cases) in the structure i pick?

Information Regarding JIRA Structure REST API is posted here https://wiki.almworks.com/display/structure/Forest+Resource

Related

How to Extract Jira test results data using azure data factory..?

I am facing the issue with extrct projects test results data from Jira using API in azure data factory.
Please help me on this..
I don't have experience using XRAY API, but I have made other API calls via ADF. Based on Xray documentation you would need to make two API calls in ADF.
Get Access Token/API Key
Use Access Token to Get Test Results
Theoretically it would look something like this using these links:
https://docs.getxray.app/display/XRAYCLOUD/Authentication+-+REST
https://docs.getxray.app/display/XRAY/Tests+-+REST#TestsREST-GettingallTestsstatuses
Step 1: Get Access Token (refer to link and screenshot here)
Step 2: Use Access Token to get Test Results (refer to link and screenshot)
This should be pretty close to what you need, but I am unable to test since I don't use xray, but I hope this helps.

SharePoint Rest API across subsites

I am trying to make a single rest api call from a top level site to get results from multiple picture libraries on multiple subsites. Is this possible and if not, what is the best way of approaching this.
I do have a rest api call to retrieve all subsites but I need to retrive results from libraries on a single request.
https://xxxx/_api/web/webs/?$select=title,ServerRelativeUrl"
Unfortunately it is not possible to query multiple lists using a single SharePoint REST API call, as to fetch data from a list you have to specify its parent web and title/ID. Usually for these kinds of queries the best choice is to utilize SharePoint Search REST API (Reference) or, if you can utilize some server side code, you can use the SPSiteDataQuery class to make fetch data from across whole sites or site collections (have a look at this article about SPSiteDataQuery).
Also, have a look at this SO question: Fetch data from multiple list sharepoint REST API in one Ajax call

Should I include post request in Express for building a public api?

So, I'm building a public RESTapi for testing so I can have my own set of data to fetch.i'm using Express and MongoDB. And I'm interested if I should add post request, because then the user could update the data in the API. So I'm interested what is the best practice when building such API?
There is a lot to an APi, so it would depend on what you're trying to achieve. As you're learning, I recommend that you start with creating a small project - for me personally, that's the best way to learn. There are also lots of courses out there, I would recommend the Nodejs course by Andrew Mead on Udemy.
So, getting down to it, try and create a simple todo api where the user can add a todo, update and delete it. This would require POST, PATCH and DELETE requests to be sent. (check out postman for sending API calls easily). Finally, a GET request would retrieve all the todos.
I would also recommend looking into userIds, timestamps and JWT tokens to authorize users.
Check out my github (repository named MongoDB), I've done a small tutorial on something similar...
www.github.com/nugoo1

Regarding REST API

I'm new to REST APIs and trying to understand the basics of them. So lets begin by saying that I have created a simple CMS web application using PHP (You create an user, you post an entry and assign some categories maybe, etc...).
That being said, if I wanted to create a mobile app that would do the same, I'll have to create some PHP functions in order to send data as JSON or XML and also in order to process a POST or PUT request.
is a REST API the collection of those functions I'd use to handle the mobile app POST, PUT and GET request using JSON or XML as the data format? if not, can I get an example, not a definition, please.
To answer your question,yes, the REST API is a collection of those functions for any client you wish to expose it to for creating an user, posting an entry etc. The accepted data format is something you decide for your API. It may be JSON, XML or even both.
Some examples:
http://coenraets.org/blog/2011/12/restful-services-with-jquery-php-and-the-slim-framework/
http://peter.neish.net/building-a-mobile-app-backend-using-mongodb-and-slim-a-php-rest-framework/

How do i use an API

I've never used an API and was wondering how you use them... I would like to use facebook, twitter and vimeo's api,
Can someone explain the basics of using them, how do i access them and use them etc.
Please and thanks
Neil
How to use an API depends on the API. Usually the API creator has documentation on how to use their specific API.
Mostly, things work like the following:
You register to get a developer key. Then, you send requests to the service via HTTP (for example Twitter is using REST, which requires you to send XML or JSON to a specific http-URL providing your key). You get an answer from the service, which you must then parse and react to accordingly (for example filling a list with contacts, etc.).
Most of the time this all comes down to:
Create an XML or JSON document that describes the call parameters
Send the document to an URL using GET, POST or other request methods
Get the server's response
Parse and evaluate the response
The specific ways to use the API, especially performing authentication, can be found on the service's developer pages.
The best way to start if you want to use an API is to read it's documentation, find some tutorials and code examples. This is always/usually published by the one offering an API.
Good luck :)