DZone
Integration Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Integration Zone > Box's Seamless Approach To API Documentation

Box's Seamless Approach To API Documentation

We'll never see things move as fast as we want—but eventually, the world evolves. We'll see investment in areas that make a difference on the ground at API operations.

Kin Lane user avatar by
Kin Lane
·
Feb. 27, 17 · Integration Zone · Opinion
Like (3)
Save
Tweet
4.03K Views

Join the DZone community and get the full member experience.

Join For Free

The document platform Box updated their developer efforts recently, helping push forward the definition of what API documentation can be. I've long been advocating moving APIs out from the shadow of the developer portal making them more seamless with any UI, kind of like CloudFlare does with their DNS dashboard. There is no reason the API should have to be hidden from users — it should be right behind the UI for everyone to discover.

Box does this. You can interact with files just like it is the regular interface. When you push get the folder items, upload file, or any other option available to you in the documentation, you get an example API request and response in the right-hand column. It is a blend of a regular UI and some of the attractive and interface documentation we've seen emerge lately, like ReDoc — making it easy to see and understand what an API does, while speaking in the context of solving a relevant problem for a human.

API documentation doesn't have to be overly technical and boring. It can look like a regular user interface, and the API can be right behind the UI curtain, providing a snapshot of the requests and responses that are doing the heavy lifting behind. I'm finally seeing the movement I have wanted to see with API documentation in 2017. I'm feeling like this is going to be a common theme in the world of APIs for all of us. We will never see things move as fast as we want, but eventually, the world evolves — and we will see investment in the areas that make a difference on the ground at API operations and for the consumers who are putting APIs to work in their regular world.

API Documentation

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • How to Build Security for Your SaaS User Communications
  • Which JVM Version Is the Fastest?
  • AWS IAM Security Best Practices
  • Event-Driven Microservices?

Comments

Integration Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo