Ratebeer API access?

I’ve been using my key for months in IE6.

I’ve found a solution to the problem I think. Here are the constraints

1. ratebeer can’t withstand unlimited use of its services so usage needs to be monitored and limited

2. ratebeer and the craft beer community deserve to share in any rewards for development with the API

3. monitoring the keys and projects out there takes some time and attention

There is still some abuse. Some I overlook. For some I needed to revoke keys but no biggie.

Here’s what I’ll do:

1. Set the number of available keys to 100
2. Perform quarterly reviews and eliminate unused keys, booted API users’ keys
3. Use these new slots to offer additional keys
4. Post the number of keys available
5. Require API requests come with a brief proposal
6. State the type of projects preferred by RateBeer based on our Mission Statement and current interests
7. Allow Eric to moderate this list

Does this sound good?

Looks fair enough to me, so long as the information is transparent and readily available and the reviews do happen on a proper schedule. I think this is a very fair system. What’s the possibility of the keyholders being listed publicly, along with a link to their project? Especially considering the desire to have the craft beer community having a share in the rewards, it seems fair, and would create good traffic to their app.

Originally posted by puzzl
Looks fair enough to me, so long as the information is transparent and readily available and the reviews do happen on a proper schedule. I think this is a very fair system. What’s the possibility of the keyholders being listed publicly, along with a link to their project? Especially considering the desire to have the craft beer community having a share in the rewards, it seems fair, and would create good traffic to their app.

The API key holder should be able to opt in or out of public view.

We’ve had a fair number of key holders who were using RB data in proprietary research and we were under NDA. A number of other partnership projects were kind enough to share their development with RateBeer on condition we did not expose their work to the public.

There are many though who would probably enjoy the exposure. This is something we’d happily provide!

That sounds like a very good plan Joe, and I am happy to help out. Asking for a proposal with every RateBeer key seems fair and a public list (opt out) can help the community see what’s been done with their data.

I’m in the same boat. How much cash do I send, and has that helped??

Originally posted by TheBeerShopLTD
How much cash do I send

$12.99 for a premium membership would probably be a good start.

Originally posted by joet
Here’s what I’ll do:

1. Set the number of available keys to 100
2. Perform quarterly reviews and eliminate unused keys, booted API users’ keys
3. Use these new slots to offer additional keys
4. Post the number of keys available
5. Require API requests come with a brief proposal
6. State the type of projects preferred by RateBeer based on our Mission Statement and current interests
7. Allow Eric to moderate this list

Does this sound good?

This all sounds good. Should those of us who have sent API requests via email in the past continue to wait for a reply?

I know that Joe is working on this at the moment, but things more a bit slow. He has contacted me to start this better allocation process of API keys, but I’m afraid more patience is required.

Originally posted by erickok
I know that Joe is working on this at the moment, but things more a bit slow. He has contacted me to start this better allocation process of API keys, but I’m afraid more patience is required.

Thanks for the info. Should us impatient people continue to check this thread or somewhere else? :)