We are delighted to have people use our feeds and look to continue this free service. However, the explosion in usage means we need to manage this finite resource. For most users, API access is obtained by answering our questionaire. This coupled with some minor changes in your query will get you up and running quickly.
We welcome any and all suggestions around improvements to the feed.
Additionally, if you need custom information generated in machine readable formats (.json, .xml, .csv, .bson), we would be delighted to discuss this with you. Use our form to get the process started.
Rules (click to expand)
The feeds are provided with no guarantees, neither implied nor expressed. You use the info at your own peril.
If you redistribute, post or display our information in your service or website, we request you attribute our content to us.
We can terminate your usage for any reason whatsoever.
The questionaire will collect your name, email address and phone number. We will save this info in our db. We have no interest in selling this info to anyone. The information allows us to know who you are. We may send a status check email from time to time.
Do not share your login tokens. The backend is 100% automated. We keep track of the site requests to make sure it runs correctly. If there is abnormal usage from your script we will make an attempt to let you know and if that does not remedy the situation, we will cut you off.
The approval process DOES involve a human responding to your request. Once you send in your info, give us a bit of time to process it and set up the user.
Your Digest/Basic auths will only work on the feed/api endpoints. They will not work on other access controlled endpoints. This is by design. We would rather avoid using user/password schemes since they require more interactivity. The API auth stuff is the exception. While you can use OAUTH2 to enable API access, our experience has not been terribly great with that approach.
Please report any issues you have running with this setup. We have tested it and have a cURL example posted.