The VersionOne api parameter does not serve images and does not display specific data. You can use the query language and the rest of the endpoint to obtain the data needed for burnout. You will need to be able to read / analyze data and create a chart yourself.
With that said, the graph of the burnt image compares how closed the score is compared to how many open ratings and graphs are over time. Therefore, you need to know three pieces of data: open rating, closed rating, and time. You will also want to limit it to a specific project (and these will be children).
This will help you get closer to the data needed to burn the project:
http://<host>/VersionOne/rest-1.v1/Data/Timebox?where=Schedule.ScheduledScopes='Scope:1055'&sel=Name,BeginDate,EndDate,Workitems:Story[AssetState!='Closed'] .Estimate.@Sum ,Workitems:Story[AssetState='Closed'] .Estimate.@Sum &sort=+EndDate
Be sure to change the scope: 1055 to a project that interests you.
This is how I got there. At first I thought: “Well, you need to take stock of the story’s assessment,” so I thought I would make a historical request for stories:
http://<host>/VersionOne.Web/rest-1.v1/Hist/Story?where=Scope.ParentMeAndUp='Scope:1055'
But quickly discovered that you can’t populate your root directory. This means that if I want to summarize, I need to use something else, such as Project (scope), to get the data:
http://<host>/VersionOne.Web/rest-1.v1/Hist/Scope/1055?sel=Workitems:Story[AssetState!='Closed'] .Estimate.@Sum ,Workitems:Story[AssetState='Closed'] .Estimate.@Sum ,ChangeDate
The problem with this query is that the open and open evaluation looked like weird intervals; namely, when the project has changed. Thus, this will not make a very beautiful schedule.
But, as you know, VersionOne has the concept of Iterations and Schedules, which are related to the project, and the stories are related to iterations. Therefore, I used this as the root to query and aggregate plot ratings and limited the data to projects using this schedule.
The data obtained are more regular (grouped by iteration) and contain correctly aggregated assessment data.
So what's left? You will need to aggregate the aggregation of the assessment data in order to get a common evaluation number for your project. Then you will need to create a graph (possibly a row or row) where each data point is at the end of the iteration. You will save the current total amount of the closed estimate and add it to the total iteration to create a data point.