Coming soon
Streamitter API
A future programmatic interface for developers, hardware makers, apps, broadcasters, and platforms to integrate Streamitter's global live radio directory: discovery, metadata, and partner-ready workflows. Not available yet, this page is a preview of direction and intent.
Waitlist opens the form with that inquiry type selected. For other API or business questions, open API business contact. No API keys are issued from this page.
What the API will be for
Streamitter is a radio-first directory of live online stations, organized by country, genre, and search. The future API will expose that same worldview to software: clean metadata, predictable filters, and room to grow into authenticated broadcaster tools.
Partners will be able to power apps, websites, dashboards, infotainment systems, smart speakers, and embedded players with data that matches what listeners see on Streamitter.com. The focus stays on live radio, not podcasts, with HTTPS streams and compatibility in mind.
Down the road, authenticated endpoints can support favorites, likes, station management, analytics, and carefully scoped stream information, always aligned with broadcaster control and platform safety.
Signals that matter to Streamitter
Twelve principles we expect the program to emphasize alongside the feature grid. They keep integrations honest, global, and on-brand.
Discovery stays centered on live stations, not on-demand shows.
Documentation will echo Streamitter's secure-stream requirement.
Shareable permalinks that match the public site.
Predictable /v1 style paths so partners can plan migrations.
Likes, favorites, and plays inform lists where policy allows.
Availability cues to build reliable play buttons.
Same taxonomy listeners browse today.
Curated rails for partners who want Streamitter taste-making.
Metadata flows from owners and moderators, not scrapers.
Logos, names, and links follow station-provided assets.
Packaging for long-lived fleet software and OEM review.
Future hooks when listings or status shift.
What partners could build on
Illustrative feature areas. Availability, authentication, and fields will be confirmed in real developer documentation.
Discovery and search
Station directory access
Browse the catalog programmatically with pagination and stable ordering options.
Possible use cases
Home screens, “near me” radios, editorial picks.
Search stations by keyword
Full-text style queries across names, taglines, and related fields tuned for radio.
Possible use cases
Voice assistants, in-car search, mobile apps.
Filter by country
Align results with Streamitter's country model used on the public site.
Possible use cases
Travel apps, regional guides, border-crossing infotainment.
Filter by genre
Use the same genre taxonomy listeners already trust on stream pages.
Possible use cases
Genre hubs, mood-based UIs, smart radio presets.
Filter by language
Surface stations by primary language metadata for global audiences.
Possible use cases
Immigrant communities, language-learning companions.
Sort by popularity
Rank by listening and engagement signals the directory already emphasizes.
Possible use cases
Trending rails, “most played” car rows.
Sort by latest added
Highlight fresh listings for editors and algorithmic “new on Streamitter” shelves.
Possible use cases
Newsletters, creator tools, onboarding flows.
Sort by likes and favorites
Optional authenticated or aggregated engagement signals for ranking.
Possible use cases
Community charts, social proof in players.
Station detail and streams
Get station details
Retrieve core metadata: name, slug, tagline, description, country, genres, language, branding.
Possible use cases
Detail pages in third-party apps, CRM enrichment.
Stream status and availability hints
Signals such as last check timestamps or online indicators to build reliable players.
Possible use cases
Auto-hide broken streams, retry logic in embedded players.
HTTPS-first stream philosophy
Documentation will reflect Streamitter's focus on secure streams and broad device support.
Possible use cases
Automotive certification, enterprise security reviews.
Website and social links
Official URLs for websites, X, Facebook, Instagram where broadcasters publish them.
Possible use cases
Deep links from dashboards, social previews.
Logos and branding assets
Pointers to approved logos and thumbnails for consistent rendering across surfaces.
Possible use cases
Car tiles, TV grids, kiosk displays.
Related and similar stations
Recommendations based on genre, geography, and listening patterns.
Possible use cases
End-of-session suggestions, cross-sell in aggregators.
Trending and featured rails
Curated and algorithmic lists: trending, featured, editorial collections.
Possible use cases
Home screens, partner bundles, campaign placements.
Recently added stations
Time-ordered feeds for editors and power listeners.
Possible use cases
RSS-style digests inside partner apps.
Directories, broadcasters, and trust
Country directory endpoints
List countries with counts and slugs aligned with public URLs.
Possible use cases
Map-first UIs, travel modes.
Genre directory endpoints
Genre metadata and popularity context for filters.
Possible use cases
Onboarding pickers, smart speaker slots.
Language directory endpoints
Language metadata for multilingual discovery.
Possible use cases
Hotel apps, airline IFE.
Station claim and owner workflows
Future authenticated flows to tie listings to verified broadcasters.
Possible use cases
Self-serve corrections, partner onboarding.
Broadcaster profile hooks
Roadmap-friendly endpoints for dashboard actions mirrored in integrations.
Possible use cases
CMS plugins, multi-station owners.
Likes, favorites, and engagement
Authenticated actions where policy allows, respecting listener accounts.
Possible use cases
Cross-device favorites, partner loyalty.
Embeddable player alignment
Metadata and launch patterns that complement Streamitter player experiences.
Possible use cases
Broadcaster sites, partner iframes.
White-label directory patterns
Partner layouts that keep Streamitter data fresh while matching your brand.
Possible use cases
Telcos, OEM start screens.
Scale, analytics, and operations
Rate limits and fair use
Predictable quotas for public tiers and higher ceilings for partners.
Possible use cases
Mobile launches, burst traffic during events.
API keys and tokens
Key-based access for partners, scoped tokens for user-authorized features.
Possible use cases
Server-to-server integrations, mobile SDKs.
Broadcaster analytics (roadmap)
Aggregated visibility into how integrations surface a station.
Possible use cases
Program directors, network groups.
Verification and moderation
Workflows that align with Streamitter's quality bar for live listings.
Possible use cases
Enterprise compliance, brand safety.
Webhooks (concept)
Optional callbacks when metadata or availability signals change.
Possible use cases
Cache invalidation, monitoring pipelines.
Enterprise and automotive programs
Dedicated onboarding for OEM, hospitality, and hardware partners.
Possible use cases
Long sales cycles, custom SLAs.
Versioned API surface
Clear /v1 style namespaces so partners can migrate on a schedule.
Possible use cases
Stable infotainment stacks, multi-year contracts.
Geo-aware availability (future)
Signals that respect broadcaster geo rules where the product exposes them.
Possible use cases
Cross-border compliance, roaming listeners.
Built for partners, broadcasters, and developers
Whether you ship consumer apps, fleet software, or broadcaster tooling, the same metadata spine can power discovery while respecting Streamitter\'s live-radio mission.
Ship a polished discovery layer without rebuilding a global station graph.
Infotainment rows that stay fresh with trending, regional, and genre slices.
Voice-first search that returns structured station objects for playback.
Blend Streamitter metadata with your editorial voice and rankings.
Mirror public metadata into your own ops tools and alerting.
Track live sources with consistent IDs and stream endpoints where permitted.
Local radio by airport, city, or country for guests and passengers.
Civic, campus, and nonprofit hubs that highlight live stations first.
Pair official metadata with your branded embed experiences.
Controlled playlists backed by licensed live sources where appropriate.
Example endpoints (not live)
The snippets below are illustrative. Final base URLs, versioning, pagination, and authentication headers will ship with official docs. Treat this as a conversation starter for product and engineering teams.
GET /api/v1/stations
GET /api/v1/stations/{id_or_slug}
GET /api/v1/countries
GET /api/v1/genres
GET /api/v1/search?q=jazz&country=US
GET /api/v1/trending
GET /api/v1/recently-added
GET /api/v1/stations/{id_or_slug}/related{
"id": 120491,
"slug": "example-fm-live",
"name": "Example FM Live",
"tagline": "Non-stop hits from your city",
"description": "A sample object for documentation. Fields may change.",
"country": "United States",
"country_code": "US",
"language": "English",
"genres": ["Pop", "Top 40"],
"website": "https://example.com",
"logo_url": "https://cdn.example/streamitter/logo.webp",
"stream_url": "https://listen.example/stream",
"is_verified": true,
"is_featured": false,
"is_online": true,
"social_links": {
"x": "https://x.com/examplefm",
"facebook": "https://facebook.com/examplefm"
},
"last_checked_at": "2026-04-12T10:15:00Z",
"created_at": "2024-02-01T12:00:00Z",
"updated_at": "2026-04-10T08:42:00Z"
}Stream URLs, social data, and verification flags will always follow broadcaster permissions, moderation, and regional rules. Some fields may remain web-only depending on your access tier.
Authentication and access (planned)
Public read tiers
Expect a conservative, rate-limited tier for anonymous access to select directory data, ideal for experimentation and lightweight consumer apps.
API keys and tokens
Partners would receive keys for server-side use. User-delegated flows could use short-lived tokens where listeners opt in.
Access tiers
Higher tiers unlock richer engagement data, webhook subscriptions, higher rate limits, and priority support for automotive or enterprise rollouts.
Rate limiting
Protective quotas keep the directory fast for listeners while giving serious partners predictable capacity and upgrade paths.
Why broadcasters should care
- Wider distribution: your metadata reaches apps, cars, and devices without rebuilding every integration yourself.
- Consistent story: one canonical record for names, logos, genres, languages, and links across partners.
- Discoverability: trending, search, and related-station surfaces help new listeners find you in context.
- Operational clarity: future analytics and status hooks can show how integrations perform, always within Streamitter policy.
- Control over time: roadmap features aim to keep owners in charge of branding, descriptions, and stream presentation rules.
Automotive, smart home, and embedded experiences
Live radio shines where people already listen: moving vehicles, kitchens, hotel rooms, retail floors, and lean-back TV. Streamitter\'s global catalog is a natural fit for infotainment, smart speakers, TV apps, embedded Linux players, and OEM partnerships that need trustworthy metadata at scale.
We expect to work closely with automotive, hospitality, and hardware teams on certification-friendly documentation, stable versioning, and partner support that respects the long lifecycles of fleet software.
API program FAQ
Building an app, device, or platform with radio?
Tell us what you want to ship. We will keep you in mind as the API program opens and documentation goes live.
