sattvinfo.net APIsattvinfo.net ↗
Access satellite TV data from SatTvInfo.net: transponders, channel PIDs, BISS keys, HD/UHD satellite lists, TV packages, and country-based channel lookup.
curl -X GET 'https://api.parse.bot/scraper/c13f9604-02d5-45aa-8c82-eedf4ae0918c/get_satellite_list?lang=en' \ -H 'X-API-Key: $PARSE_API_KEY'
Get the full list of satellites with names, orbital positions, and frequency bands.
| Param | Type | Description |
|---|---|---|
| lang | string | Language code: 'en' or 'ru'. |
{
"type": "object",
"fields": {
"satellites": "array of satellite objects with name, sat_id, position, and band"
},
"sample": {
"data": {
"satellites": [
{
"band": "C",
"name": "NSS-9",
"sat_id": "1831e",
"position": "183.1E"
},
{
"band": "C/Ku",
"name": "ABS-6",
"sat_id": "1590e",
"position": "159.0E"
}
]
},
"status": "success"
}
}About the sattvinfo.net API
The SatTvInfo.net API exposes 8 endpoints covering satellite transponders, channel PID data, BISS encryption keys, and TV package listings sourced from sattvinfo.net. get_satellite_channels returns full transponder breakdowns per satellite — including frequency, symbol rate, FEC, provider name, and per-channel PIDs with encryption flags. Additional endpoints cover HD and Ultra HD satellite filtering, country-based channel lookup, and orbital-position queries.
Satellite and Transponder Data
The core get_satellite_channels endpoint accepts a sat_id (obtained from get_satellite_list) and returns an array of transponder objects. Each transponder includes txp_no, source_date, freq_pol_mode, sr_fec, provider_name, footprints_eirp, and a channels array with per-channel PIDs and encryption details. The equivalent get_satellite_by_position endpoint accepts an orbital position string such as '13.0E' or '4.0W' and returns the same transponder structure without needing a sat_id lookup first.
BISS Keys and Encryption Info
get_biss_keys returns an array of objects each carrying satellite, frequency, sr, channel_name, biss_key, and standard. This is useful for receivers that need BISS (Basic Interoperable Scrambling System) keys to decode specific channels. Channel names and some metadata are localized when the optional lang parameter is set to 'en' or 'ru'; both language codes are accepted across all endpoints.
HD, Ultra HD, and Package Listings
get_hd_channels and get_ultra_hd_channels return filtered satellite lists — specifically those carrying HD or UHD (4K) content — with name, sat_id, position, and band fields. These lists can feed directly into get_satellite_channels calls to retrieve the transponder detail for those satellites. get_tv_packages returns a flat list of satellite TV packages worldwide with name and package_id fields.
Country-Based Channel Lookup
get_tv_by_country behaves differently depending on whether country_code is supplied. Without it, the endpoint returns a countries array of objects with name and code. With a two-letter code such as 'ru' or 'de', it returns a channels array where each entry includes satellite, frequency, sr_fec, channel_name, v_pid, a_pid, sid, and footprint. Coverage varies: well-documented regions like Russia and Germany return extensive data while less-covered countries may return empty results.
- Build a satellite dish alignment tool using orbital positions and transponder frequency/polarization data from
get_satellite_by_position. - Populate a DVB receiver configuration with channel PIDs, SID values, and FEC settings pulled from
get_satellite_channels. - Maintain an up-to-date BISS key database for encrypted sports and pay-TV feeds using
get_biss_keys. - Filter a satellite list to only HD or UHD sources using
get_hd_channelsorget_ultra_hd_channelsbefore drilling into transponder detail. - List all satellite TV packages available in a given region by combining
get_tv_packageswithget_tv_by_country. - Generate a country-specific channel guide with footprint and frequency data for a set-top box setup wizard.
- Cross-reference provider names and footprint EIRP data from transponder objects to compare coverage areas across satellites.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does SatTvInfo.net have an official developer API?+
What does `get_satellite_channels` return beyond just a channel list?+
transponders array where each object includes txp_no, source_date, freq_pol_mode, sr_fec, provider_name, and footprints_eirp, plus a nested channels array with individual channel PIDs and encryption flags. The sat_id input is required and must come from a prior get_satellite_list call.Is country coverage consistent across all countries in `get_tv_by_country`?+
ru) and Germany (de) have extensive channel data, while many others may return empty channels arrays. Omitting country_code entirely returns the list of countries that have any data at all, which is a useful pre-filter before making country-specific requests.Does the API support searching for a specific channel by name across all satellites?+
Can I retrieve historical transponder changes or frequency update logs?+
source_date field indicating when the entry was last recorded, but the API does not expose a changelog or historical diff endpoint. You can fork this API on Parse and revise it to add an endpoint that tracks and surfaces transponder change history.