The first thing any consumer of an API will see is the landing page. Just like the home page of a website, the API landing page should speak to the target audience, telling them of the value the API possesses and providing single click access to every aspect of the API.
On the API landing page, the first thing a user should see is a short, descriptive paragraph explaining the value delivered by the API. There is no need talk about REST or JSON, API owners should explain what problems the API solve, in a language anyone will understand. Don’t assume anything about visitors. In all likelihood the user will know nothing about the company, products and history.
Each API landing page should speak to as wide an audience as possible, even non-developers, rising above the technological jargon and clearly explain the business value delivered by an API.
Latest Blog Posts
- Connect With Linguistics API Apicultur While They Are In San Francisco
- My First Keynote With The Infamous Audrey Watters
- Are You Going To Be At API Days in San Francisco? I Am!
- Updated API History White Paper
- History of APIs - Twilio
- API Providers Guide - API Design
- Box Opens Up Revenue Sharing For API Developers
- History of APIs - Mashery
- A Book API Platform
- History of APIs - del.icio.us
- API Management Using Github
- In The End API Providers Will Only Sell Bandwidth
- The Build-Up To #APIStrat in October
- APIdays Mediterranea Is A Wrap
- Helping EFF Urge The Courts to Block Copyright Claims in Oracle v. Google API Fight
- API Aggregation For Federal Government with FedAPI
- Have You Checked Out Webshell Lately?
- New Features From BaaS Provider AnyPresence
- Signals I Use To Monitor Companies In The API Space
- API Management Using APiphany
- Github Can Be More Than Code
- Quick Demonstration Showing The Benefits of The White House Digital Strategy
- IRS Needs To Use White House Open Data Policy For Guidance
- Dropbox As Your Apps Default File System
- DataSift's Open Source World