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, Attribution, Brand, Branding Guidelines|
blog comments powered by Disqus
Latest Blog Posts
- Dropbox As Your Apps Default File System
- DataSift's Open Source World
- Salesforce Adds Sandbox Templates
- An Open Source Code Catalog for your API
- Multi-Tenancy with WSO2 API Manager
- Ember, Angular, Backbone, Single Page Applications and APIs
- APIs in DFW
- Adding API Broker Under Monitoring for API Aggregators
- The Dark Matter That Make APIs Work
- Potential for API Aggregators to Provide Valuable Industry Data
- My Talk Tomorrow Night at the Dallas-Forth Worth API Professionals Meetup
- The White House Releases An Open Data Strategy
- When API Success Signals Begin Working Against You
- Get To Know Which Languages Your API Developers Are Using
- Twitters Developer Area is More Embeddable Than API
- Overview Of Backend as a Service (BaaS) White Paper
- Make Sure And Have Multiple KPIs For Your APIs
- API Enabled Toys For Our Children
- I Am Speaking At The Dallas-Forth Worth API Professionals Meetup May 14th
- How Much Do You Spend Attracting and Supporting Freemium API Developers?
- What Does The API Evangelist Do?
- Startups Need To Work Together on API Definitions
- Parse Is Successful By Truly Solving Problems for Mobile Developers
- API Commandment: Thou Shalt Not Forego Talking to a Person
- API Trends