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 read #6 from 2015, where it was discussed for which endpoints query parameters was supported.
Issue
However, even though some endpoints may not have unique query parameters, all resources looks at fields which determines what fields should be included in the response.
When making a request, the client can explicitly determine which attributes of each resource should be returned by sending the fields parameter. This parameter and its effects are described in Selecting Attributes to Include in Responses.
I read #6 from 2015, where it was discussed for which endpoints query parameters was supported.
Issue
However, even though some endpoints may not have unique query parameters, all resources looks at
fieldswhich determines what fields should be included in the response.^ from section Response Customisation
My case
When I GET a story it doesn't include all the fields I want. You can see what fields it sends by default here; https://www.pivotaltracker.com/help/api/rest/v5#story_resource
Proposed solution
Add support for "options" (query parameters) for all endpoints.