When creating paid resources like Radio Streams or Transcoders with the API, a billing plan must be specified. Each billing plan is uniquely identified by a short "slug" string.
All resources are billed by the hour. For pricing and more information about billing, see Pricing.
This page lists all possible values for the billing plan field, for each resource type:
Radio Mast-hosted streams have a
streaming_plan field that must be one of the following.
Standard streaming plans (MP3, AAC, AAC+, Ogg Vorbis, or Ogg Opus):
100L-64- 100 listeners / up to 64 kbps
200L-128- 200 listeners / up to 128 kbps
300L-128- 300 listeners / up to 128 kbps
400L-128- 400 listeners / up to 128 kbps
800L-320- 800 listeners / up to 320 kbps
1600L-320- 1600 listeners / up to 320 kbps
Lossless (FLAC) streaming plans:
lossless-100- 100 listeners / FLAC
lossless-200- 200 listeners / FLAC
lossless-400- 400 listeners / FLAC
lossless-800- 800 listeners / FLAC
lossless-1000- 1000 listeners / FLAC
Both Radio Mast and External Radio Streams can have Stream Monitoring turned on by setting the
plan field nested
monitoring. Possible values for the monitoring plan are:
basic- Stream uptime monitoring
silence_detection- Stream uptime monitoring and silence detection
null- Monitoring will be disabled
For more information on configuring monitoring via the API, please see Monitoring.
API users have access to a special "auto-scaling" streaming plan, which can offer cost savings for developers with large numbers of audio streams and highly variable listener counts. The auto-scaling plan has no listener limit and is billed according to the total listener hours (TLH) and bitrate streamed.
The auto-scaling plan can be used by setting the
streaming_plan field to
The base price is $0.000075 per listener hour at 64 kbps, and scales linearly based on the bitrate.
Auto-Scaling Pricing Examples:
|TLH||32 kbps||64 kbps||128 kbps||192 kbps||320 kbps|
The TLH is measured based on the 95th percentile listenership for each hour. A listener hour is defined as a listener playing your stream for an hour.
Developers should consider using auto-scaling when:
Developers should consider our standard streaming plans when:
Questions about pricing? Get in touch and we'd be happy to help.