NPR One System & Services

System Overview

All API requests and responses use the JSON data interchange format and are required to be sent over HTTPS.

devcenter assets 2 systemoverview 2

NPR One Services

The NPR One API was built around the following RESTful principles, with the goal of promoting application development across a wide variety of platforms:

  • Predictable, resource-oriented URLs.
  • Built-in HTTP capabilities for passing parameters.
  • Responses using standard HTTP response codes to indicate errors.
  • Sending and receiving data as JSON.

This linked sections below provide an overview of each service, including code samples and implementation details. Please consult the API Reference page for comprehensive documentation of all API services and endpoints. 


NPR uses the OAuth 2.0 protocol to allow third-party client applications to make authorized requests for resources from the NPR One API. OAuth has been used by many services, including Facebook, GitHub, and Google.

NPR supports two OAuth grant types for third-party developers to gain access to our API resources: 

Authorization Code

Device Code 



NPR One is public radio made personal. The Listening Service provides personalized audio recommendations and collects user data that allow NPR to continuously improve the user’s listening experience. Most of the communication between NPR and your client application will occur via this service.

Audio Ratings & Recommendations 

Playing Audio



The Identity Service provides an entry point to access user-specific data, including information about their local NPR member station, shows or podcasts they are following, and days since they last listened to NPR One. 



The Station Finder Service delivers the local branding and content elements that enable your client application to provide a localized NPR One experience on your platform. This page provides documentation on station search, updating a user's preferred station, and accessing and displaying station data. 


Last modified