Frequently Asked Questions
These are the questions I get asked the most when people are getting up and running using my APIs. I try to provide answers to most of the challenges you will face, to encourage you to do everything on your own.
- Who is Kin Lane? - I am the API Evangelist, an analyst and engineer who focuses exclusively on the world of APIs.
- Why do you have APIs? - Everyone should have APIs, not just the Twitters of the world. I have APIs to help practice what I preach, and make my research open and accessible to everyone.
- What can I build with the APIs? - That is up to you. I have APis to empower you with access to my research, what you build should benefit your world, as well as the wider API community.
- What is the best way to get support? - The best way is to submit a Github issue for the master API stack, or via the Github repository for each API. I try to keep API specific issues local to each API, and wider conversations via the portal.
- Why did it take a couple days to get response? - I am a one man show, and sometimes I can get to issue immediately and sometimes it takes me time. If it is mission critical, I will make time, but otherwise I queue things up.
- Can I email you? - Sure you can, but remember that I do not always check email each day, as sometimes I tune it out to be more productive in my research. I priotize Github issues and Tweets a little differently.
- Can I talk to you on the phone? - I take calls on Thursday, and have open office hours. Schedule something ahead of time and I'm happy to carve ou the time.
- Can I use your images? - All of my content is licensed CC-BY-SA. All I ask for is attribution when it makes sense.
- Can I use repost your stories? - All of my content is licensed CC-BY-SA. All I ask for is attribution when it makes sense.
- How is your code licensed? - All code I produce tends to live in Github repository, and usually post licensing within each project--which is usually Apache 2.0.
- Can I use your API designs? - All of my APIs are licensed CC-BY-SA as well using API Commons--feel free to re-use all my designs.
If you don't find the answer you are looking for, head over to the support page, and hit me up via one of the supported channels. I encourage you to use the Github issues for this repo, so we can keep the history for others to learn from.