You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently writing a script to automatically create storyboards from my own datasets and fill them with custom information using the REST API. When it comes to creating just the storyboard, that works just fine via the /users/{userId}/storyboards path. However, filling the storyboard with items (goals, columns, stories) is currently very tedious, since the API for creating those is still very bare bones. In particular, the HTTP response for creating these items doesn't return any data.
An example for a problem I ran into was:
I create a new goal for the storyboard using the /storyboards/{storyboardId}/goals endpoint.
Now I want to create a column for my new goal, but /storyboards/{storyboardId}/columns requires me to specify the ID of the goal that the column is added to.
I have no way of knowing the ID of the goal I just created, since the response to endpoint /storyboards/{storyboardId}/goals contains a data object that is just empty.
I could search for the new goal's ID by requesting the storyboard info with GET /storyboards/{storyboardId}, but this is not a very nice or efficient way to do this IMO.
Describe the solution you'd like
Best case would be to return the JSON definition of the item that was just created. So for a new storyboard goal, I would like to see the JSON data model that is also part of the response in GET /storyboards/{storyboardId}.
Describe alternatives you've considered
If the solution above is not feasible, I would expect that the creation of a new storyboard item returns at least the ID of the created resource, so that it can be used in further requests.
The text was updated successfully, but these errors were encountered:
Description
I'm currently writing a script to automatically create storyboards from my own datasets and fill them with custom information using the REST API. When it comes to creating just the storyboard, that works just fine via the
/users/{userId}/storyboards
path. However, filling the storyboard with items (goals, columns, stories) is currently very tedious, since the API for creating those is still very bare bones. In particular, the HTTP response for creating these items doesn't return any data.An example for a problem I ran into was:
/storyboards/{storyboardId}/goals
endpoint./storyboards/{storyboardId}/columns
requires me to specify the ID of the goal that the column is added to./storyboards/{storyboardId}/goals
contains a data object that is just empty.I could search for the new goal's ID by requesting the storyboard info with
GET /storyboards/{storyboardId}
, but this is not a very nice or efficient way to do this IMO.Describe the solution you'd like
Best case would be to return the JSON definition of the item that was just created. So for a new storyboard goal, I would like to see the JSON data model that is also part of the response in
GET /storyboards/{storyboardId}
.Describe alternatives you've considered
If the solution above is not feasible, I would expect that the creation of a new storyboard item returns at least the ID of the created resource, so that it can be used in further requests.
The text was updated successfully, but these errors were encountered: