Pollster API v2

[Adam Hooper]

This affects all API users. That includes all CSV users.

It's a big one.

In 2016, we at Huffington Post tweaked the inputs for our charts and models in the run-up to the election. We added extra rows to our CSVs towards the beginning of the year. Then we added duplicate questions in July. Back then, most of you weren't on this list, so it was hard to communicate those changes. Let's be generous and call the whole 2016 situation "unstable".

Let's make promises for 2018. Let's call them "Pollster API v2."

The goal is stability. Our chosen approach: we're finally going to expose all the data we have. Our API will provide questions we're tracking that aren't on any charts. Our API will provide every single answer to a question from every poll -- even answers we count as "Other" and "Undecided". Our API will provide every poll for daily tracker polls -- even polls with overlapping date ranges.

Pollster API v2 will also provide data by "chart", the way the current API does. We'll be clear: chart data is derived data. The "Charts" API is good for inspiration and for holding Pollster accountable; but most users will probably prefer the new question-response API: it's simpler and we promise not to fiddle with it.

Everybody using Pollster's API or CSVs will need to upgrade. Here's the timeline:

1. 2016: Request For Comments. If you have concerns or ideas, please read our design document. You can comment straight on that document, or you can reply here, or you can email me directly. I love feedback.
2. Sometime in January 2017: We publish Pollster API v2. Ideally, we at Pollster can help the community revamp python-pollster, ruby-pollster and pollstR. These will be major updates.
3. August 1, 2017: We will remove the API everybody is using today.

Questions? Concerns? Suggestions? We're all ears.

Enjoy life,

Adam