Legacy show lookup by type and id, marked deprecated; use Get Show for new work
View all Streaming Availability endpoints →A legacy endpoint at /shows/{type}/{id} that the source spec labels only as Deprecated. It takes two required path values, type and id, both strings, and declares no query parameters, so there is no country, output_language or series_granularity control on this path. The spec provides no description, allowed values or examples for either path value. No sample call was made for it and no response example was supplied, so its response fields are undocumented here and should not be assumed to match any other endpoint; verify the output yourself before relying on it. For new integrations use Get Show at /shows/{id}, which accepts an internal id, an IMDb id (tt followed by digits) or a TMDb id (movie/<number> or tv/<number>) and adds the optional country, output_language and series_granularity inputs. This entry exists mainly so existing callers can recognize the old path and plan their migration.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/streaming-availability/deprecated API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/streaming-availability/deprecated?key=<API_KEY>&id=<id>&type=<type>'
Query Result
Use Cases
- Auditing client code, proxies and request logs for calls to the /shows/{type}/{id} path before it is retired
- Keeping an older integration alive for a short window while its lookups are moved over to the single-show endpoint
- Building a migration checklist that maps every legacy type and id pair to an IMDb, TMDb or internal id
- Adding a lint or CI rule that flags newly written code that still targets the deprecated path
- Diffing legacy and Get Show responses for the same title during cut-over testing to confirm no field your app relies on is lost
Frequently asked questions
Should I use the Deprecated endpoint in a new integration?
No. It is labelled Deprecated in the source spec. Use Get Show at /shows/{id} instead, which takes an internal id, an IMDb id or a TMDb id and supports country, output_language and series_granularity.
What inputs does the Deprecated endpoint take?
Two required path strings, type and id, in the form /shows/{type}/{id}. No query parameters are declared. The spec gives no descriptions, allowed values or examples for either path value.
What does the Deprecated endpoint return?
The response is not documented. The source spec has no response example for this path and no sample call was made, so its fields are unverified. Do not assume it matches Get Show; test it against your own ids if you must keep an old caller running.
How do I migrate from this path to Get Show?
Call /shows/{id} with an internal id, an IMDb id such as tt0120338, or a TMDb id written as movie/<number> or tv/<number>; the id type is detected automatically. Then add country to limit availability to one market, output_language for en, es, tr or fr text, and series_granularity to control season and episode detail.
Can I filter by country or language on the Deprecated endpoint?
Not through any declared parameter. Only the type and id path values exist on this operation. Country, output language and series granularity are available on Get Show.
Is there a removal date for the Deprecated endpoint?
The supplied spec does not give one. It only marks the path as Deprecated, so plan your migration now rather than waiting for a notice.