GET /userstories
Fetches the list of user stories associated to the account. The account is determined by the API key.
- The amount of results returned for each page can be set by the “size” parameter.
- Pagination is done using “page” parameter.
Resource URL
GET https://api.prodpad.com/v1/userstories
Response
Status: 200 OK
[
{
"id": "5354",
"title": "Fast learning",
"story": "As a user,
I want to be able to play music easily,
so I'm not slowed down",
"acceptance_criteria": "",
"created_at": "2013-01-28 12:42:44",
"updated_at": "2013-01-28 12:43:27",
"ideas": {
"id": "1388"
}
},
{
"id": "8425",
"story": "As a user,
I want to access new music suggestions,
So that I never get bored of listening to the same songs",
"acceptance_criteria": "* Display a list of recommended songs based on behavior
* User can play songs or browse through albums by swiping",
"created_at": "2014-05-19 22:48:55",
"updated_at": "2014-05-19 22:48:55",
"ideas": {
"id": "2801"
}
}
]
Notes:
- All dates are in UTC
- The text fields can include HTML markup
Returns a specific user story.
Resource URL
GET https://api.prodpad.com/v1/userstories/:id
Response
Status: 200 OK
{
"id": "8425",
"title": "Fast learning",
"story": "As a user,
I want to access new music suggestions,
So that I never get bored of listening to the same songs",
"acceptance_criteria": "* Display a list of recommended songs based on behavior
* User can play songs or browse through albums by swiping",
"created_at": "2014-05-19 22:48:55",
"updated_at": "2014-05-19 22:48:55",
"ideas": {
"id": "2801"
}
}
Notes:
- All dates are in UTC
- The text fields can include HTML markup
Was this article helpful?
2 out of 2 found this helpful
Unless you plan to flesh out the "ideas" value in the userstory dict with more key:val pairs, you should return a list of idea ids rather than a dict of "id": "1234"