notify.io urls

[briandunnington]

the current developer info contains the following information
regarding how to send a notification:

- The URL to our API is constructed like this: http://api.notify.io/v1/notify/<md5
hash of an email for somebody you want to notify>
* For example: http://api.notify.io/v1/notify/bb46488d2c90d51f366cafc776e2b3ad
- You need to authenticate over HTTP using your API key as your
username. Your password can be empty or an arbitrary string

however, the sample client i wrote a few weeks ago does not
authenticate at all and sends the api_key (of the sender) as a
querystring parameter and it works just fine:

http://api.notify.io/v1/notify/<email hash>?api_key=<sender's api key>

i am prepping to release Growl for Windows with notify.io support, but
i want to make sure the API is solid and isnt going to change. is
passing the api_key in the querystring supposed to still be supported?
when you say 'authenticate over HTTP', are you referring specifically
to Basic authentication, and is this requirement just not enforced yet?

[Jeff Lindsay]

Both are working. I think I'll maintain both. What do you think? Join the notifyio list too!

--
Jeff Lindsay
http://webhooks.org -- Make the web more programmable
http://shdh.org -- A party for hackers and thinkers
http://tigdb.com -- Discover indie games
http://progrium.com -- More interesting things