Automate NPR Listening
HumDay reads NPR Listening’s own published API description and derives 9 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What NPR Listening is
Audio recommendations tailored to a user's preferences
API host: listening.api.npr.org
What HumDay can do in NPR Listening
1 documented operations change something in NPR Listening.
What HumDay can read from NPR Listening
These are the operations a schedule or a trigger can watch.
- GETGet a list of recent audio and aggregation items associated with search terms
/v2/search/recommendations - GETGet the list of available channels
/v2/channels - GETGet a list of media for the logged-in user from NPR's recommendation engine
/v2/recommendations - GETGet recent ratings the logged-in user has submitted
/v2/history - GETRetrieve the most recent promo audio heard by the logged-in user
/v2/promo/recommendations - GETGet a set of recommendations for an aggregation independent of the user's listening history
/v2/aggregation/{aggId}/recommendations - GETGet a variety of details about an organization including various lists of recent audio items
/v2/organizations/{orgId}/recommendations - GETGet a list of recommendations from a category of content from an organization
/v2/organizations/{orgId}/categories/{category}/recommendations
How automating NPR Listening works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live NPR Listening account.
- Grant access, then go live. You approve the specific NPR Listening operations it may use — and only those.
Popular NPR Listening integrations
Connect NPR Listening to the tools people pair it with most.
- NPR Listening and OData for namespace microsoft.graphintegration
- NPR Listening and Cloudflareintegration
- NPR Listening and NetBoxintegration
- NPR Listening and GitHubintegration
- NPR Listening and Mistintegration
- NPR Listening and Loket.nlintegration
- NPR Listening and Atlassian The Jira Cloud platformintegration
- NPR Listening and Magento B2Bintegration
- NPR Listening and Stripeintegration
- NPR Listening and Zuora Reference Billingintegration
- NPR Listening and bunqintegration
- NPR Listening and DocuSignintegration
Automate NPR Listening with these
- NPR Authorization3 operations
- NPR Identity5 operations
- NPR Sponsorship2 operations
- NPR Station Finder2 operations
- Vimeo326 operations
- Britbox Rocket121 operations
- SportsData NFL Stats76 operations
- PandaScore for All Videogames56 operations
- Haloapi Metadata37 operations
- SportsData NFL Scores36 operations
- SportsData Soccer Stats35 operations
- SportsData MLB Stats34 operations
Categories
Questions about NPR Listening automation
- Can HumDay connect to NPR Listening?
- Yes. HumDay reads NPR Listening's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 9 operations are documented.
- Do I need to write code to automate NPR Listening?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your NPR Listening account.
- What can HumDay do in NPR Listening?
- 1 of the 9 documented operations change something in NPR Listening, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my NPR Listening account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to NPR Listening is held behind that approval.
Where this came from
The operations above are read from a published API description for NPR Listening at listening.api.npr.org/v2/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.