NPR is defining new models for content distribution. One that other media providers can follow, when designing their API driven content delivery platforms.
The NPR Story API provides digital access to NPR content and to other station content--allowing both NPR and stations to contribute and consume local and national news stories.
In an effort to provide NPR stations with more control over the content they contribute to the platform for distribution, NPR Digital Services has introduced content permissions control via the NPR story API.
Currently content stored on the Story API’s platform can be retrieved by anyone with an API key--allowing content pushed across the network to be consumedd in 3 ways:
- Create Once, Publish Everywhere - Stations and npr.org push content into the API and then pull the content onto other platforms, such as other station-owned web properties and mobile apps
- Station Networks - Content is shared between multiple stations in a content network, both on web sites and mobile apps
- National - Station content is featured on npr.org and NPR mobile apps with links back to station digital properties
Using the new content permissions, stations can now control who is allowed to pull their content from the API. The permissions work by allowing stations pushing content to specify whether the content should be:
- Public to all
- Public to the NPR station network
- Public to a group of stations listed in a whitelist
- Public to everyone except for stations on a blacklist
The new changes allow stations to set these permissions at the individual story level, as well as create permission groups to add multiple stories to.
NPR's approach is a great model for how APIs can facilitate content exchange across a large network of providers, allowing for the widest distribution possible-while also allowing content owners control over who has access to their valuable content in a very granular way.
APIs are all about providing access to valuable content and resources, but should also be designed to give the proper amount of access, so your content doesn’t end up being consumed, distributed in ways you don’t find appropriate.
|Content, Media, News, NPR, Radio|
blog comments powered by Disqus
Latest Blog Posts
- 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
- API Priorities
- Have You Taken A Look At AT&T APis Lately?
- Helping People Understand APIs Through Real World Examples
- Evolving Beyond API Service Providers and Tools to Goal Based API Toolkits
- APIs & The Federal Government