Skip to content
This repository has been archived by the owner on Mar 3, 2022. It is now read-only.

White House Responses to Petitions Should Be Resources #5

Open
BigSauce opened this issue May 6, 2013 · 3 comments
Open

White House Responses to Petitions Should Be Resources #5

BigSauce opened this issue May 6, 2013 · 3 comments

Comments

@BigSauce
Copy link

BigSauce commented May 6, 2013

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 :

@nickcatal
Copy link

responses.json is in the Drupal codebase for WTP. It just isn't live on the production site yet.

@welschp @lheyman - do you have an ETA on the responses endpoint? Will it be live by the hackathon?

@welschp
Copy link
Contributor

welschp commented May 21, 2013

We don't have a specific delivery date for the responses endpoint at his stage, but it is in the queue.

@ivanstegic
Copy link

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants