One of the top five concerns I hear from companies considering APIs is regarding losing control of their brand. With APIs being about access to raw data and resources, companies immediately think that developers will extract the value, without any attribution or reference to the companies brand.
Even with this being a major concern, I see many APIs implement very poor branding guidelines, giving developers zero direction regarding how to properly provide attribution. This is a missed opportunity to not just protect the API providers brand, but actually extend it and increase its value.
With this in mind, I'm always on the lookout for good examples of API branding guidelines. One recent example I came across while monitoring my API Stack, is from the Active Network which provides activity and outdoor content via their APIs.
Active Network starts with a great explanation of why they provide branding guidelines:
At ACTIVE Network, we want you to be able to create fantastic applications with the ACTIVE Network APIs. At the same time, we don't want users to get confused about who is responsible for the data they are accessing, so we have some brand guidelines.
Next Active Network explains to developers why branding guidelines are important to their own users:
- The ACTIVE brand holds credibility in the mind of the customer. It serves as a seal of approval giving customers the confidence to transact through a trusted source
- As a consumer utility, ACTIVE.com® captures and records registration activity providing people with a record of their personal registration history if they need it at a future date
- Transacting for an ACTIVE powered activity, tells your customer who they need to call if they need help. ACTIVE’s standard of excellence provides customers with 24/7 support 365 days a year
Active Network also provides details on how to properly use their companies name (which I followed in my story), what attribution is required, and a complete branding kit for download as a zip file--containing the following key assets:
- Branding Guidelines in PDF Format
- Icon Image
- Powered by Logos
- Register Now Buttons
The Active Network Branding Guidelines is one of the better implementations I've come across. It provides a nice overview, with all of the details and assets needed to execute properly.
Even if you aren't concerned about your brand when it comes to your API, requiring some attribution from your developers will at least help you market and advertise your API, and potentially bring in new API consumers.
|Active Network, API Evangelist, Attribution, Brand, Branding Guidelines|
blog comments powered by Disqus
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