Thanks to all that attended last week's API strategy webinar "Developer Segmentation for your API" on developer community and market size. (And thanks to our speakers @sramji and @landlessness). We've included the video and slides (and as always, you are free to use under Creative Commons).
A frequent question from people who have an existing SDK is “Do I need an API?”
First, what do we mean by “SDK” and “API”?
An SDK, software development kit, is usually compiled code that is distributed to developers to embed on local devices.
An API, application programming interface, is a set of operations exposed for invocation by a remote system. (For the purposes of this discussion, we will keep the definition of an API at this high level and not delve into REST vs SOAP, good API design, etc.).
These days, SDKs are generally used when specialized processing...
Thanks to those that joined us for last week's API how to webinar presentation "Your API is not a website". (and thanks to our speakers @gbrail and @brianpagano). We've included the video and slides are below!
Thanks to all that attended last week's API strategy webinar "Boss, we need an API". (And thanks to our speakers @sramji, @brianpagano, and @landlessness). We've included the video and slides (and as always, you are free to use under Creative Commons).
At Apigee, we've been developing a secure, robust API management platform since 2005 and have been running it in the cloud since 2008. We're proud that some of the most demanding enterprise customers like Netflix, Comcast, and GameSpy have made Apigee technology part of their API platform.
We believe that it should be easy to start working with APIs, so last week we launched a new service called the OAuth API, which takes the pain out of getting up and running with APIs that use OAuth.
The story of the OAuth API is the story of yet another function...
Thanks to all that attended last week's webinar: OAuth: The Big Picture (slides and video here).
There were great questions - here are thoughts on those we didn't have time to discuss.
Q: Would you recommend only using oauth for passwords and usernames? What about more confidential items like card numbers? (John G)
I'm not sure I completely understand - but are you asking - if a user can authenticate to OAuth using a credit card number rather than a username/password?
That's theoretically possible but I'm not sure it's a good idea. Also, keep in mind that most credit-card...
Whether you are creating an API for internal use, partners or the wide open world of application developers - here is a tip that could help with initial adoption of your API.
Create at least one simple, open API method.
What I mean by simple and open is an API satisfying these criteria:
- no signup required
- no authentication required
- uses HTTP GET
- returns JSON
A good example - is the the Twitter public timeline API method - no signup or authentication required.
Many API teams we work with are creating sophisticated, highly secure APIs with complex authentication and authorization...