Who knew there was this much involved in putting out an API? The development side is all happy and happening, testing has been fine, we're ready to go. But. Terms & Conditions, App Development licenses, setting up back office stuff (aligning username with key with usage info with billing systems) and front-facing web portal, and figuring out how to make it work right is taking HOURS! Where's the manual that tells you if you need one key per app or one key per developer? For that matter, where's the manual for any of this? (Note to self: write Idiot's Guide to Creating an API.)
Rod is just back from mLearning conferences in California. He managed to get some cards printed up to promote the API and some people took them. Now we need to figure out what to do with the rest of them!