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
{{ message }}
This repository has been archived by the owner on Mar 3, 2022. It is now read-only.
I may have created some duplication in #14 that requests a small addition to the petition resource that adds the body of the response to the petition itself. I guess I'm torn between a second call to the API to get more info, or having that response embedded with the petition itself, which also makes sense. sigh
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Developers should be able to query for responses as resources just as they can do so with petitions.
Similarly to how developers would access petitions using the following url:
https://api.whitehouse.gov/v1/petitions/50cb6d2ba9a0b1c52e000017.json
they would likewise be able to access responses with the following url:
https://api.whitehouse.gov/v1/petitions/responses/responseID.json
An example of the format returned by this request is provided in Issue #4 :
The text was updated successfully, but these errors were encountered: