"\n\n \n \n \n \n \n TV API | TVmaze - Add TV information to your website or app.\n\n \n \n\n \n \n\n\n\n\n\n \n\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \n \n\n \n\n \n\n \n\n \n \n \n
\n
\n \n
\n \n \"TVmaze\"\n \n
\n\n \n
\n
\n
\n
\n
\n
\n \n
\n
\n
\n
\n\n \n
\n
\n Login Register\n
\n
\n
\n\n
\n
\n
\n
\n \n
Menu
\n
\n
\n
\n\n
\n
\n \n
\n
\n
\n
\n\n\n
\n
\n \n \n \n
\n
\n
\n\n
\n
\n
\n\n
\n

\n \n
\n
\n
\n\n
\n
\n \n \n\n
\n
\n \"Tvmaze\n
\n\n
\n

If you want to add TV information to your website or app then you've come to the right place!

\n\n
\n\n
\n
\n \n

\n We provide a free, fast and clean REST API that's easy to use, returns JSON and conforms to the HATEOAS and HAL principles.\n The root url is https://api.tvmaze.com and the available endpoints are documented below. If you have\n any questions or suggestions regarding the API, please post them on \n our forums.\n

\n\n

\n In addition to the free public API, there's a user-level API available for all Premium\n members. The documentation for the user API can be viewed here.\n

\n\n

To stay up to date with the latest changes, you can follow the changelog thread here.

\n

Table of Contents

\n\n \n

Endpoints

\n\n

Search

\n\n

Show search

\n\n \n

\n Search through all the shows in our database by the show's name. A fuzzy algorithm is used (with a fuzziness value of 2),\n meaning that shows will be found even if your query contains small typos. Results are returned in order of relevancy\n (best matches on top) and contain each show's full information.\n

\n\n

\n The most common usecase for this endpoint is when you're building a local mapping of show names to TVmaze ID's and want\n to make sure that you're mapping to exactly the right show, and not to a different show that happens to have the same name.\n By presenting each show's basic information in a UI, you can have the end-user pick a specific entry from that list, and\n have your application store the chosen show's ID or URL. Any subsequent requests for information on that show can then be\n directly made to that show's URL.\n

\n\n \n\n

Show single search

\n\n

\n In some scenarios you might want to immediately return information based on a user's query, without the intermediary step of\n presenting them all the possible matches. In that case, you can use the singlesearch endpoint which either returns exactly one result,\n or no result at all. This endpoint is also forgiving of typos, but less so than the regular search (with a fuzziness of 1\n instead of 2), to reduce the chance of a false positive.\n

\n\n

\n As opposed to the regular search endpoint, the singlesearch endpoint allows embedding additional information in the result.\n See the section embedding for more information.\n

\n\n

\n Beware that if multiple shows exist with an identical name (for example, Top Gear) it's undefined which of them will be\n returned by this endpoint. If you want to be sure you're matching with the proper show, use the search endpoint instead.\n

\n\n \n\n\n

Show Lookup

\n\n

\n If you already know a show's thetvdb or IMDB ID, you can use this endpoint to find this exact show on TVmaze. If the given\n ID can be matched, a HTTP 301 redirect to the show's URL will be returned. Otherwise, a HTTP 404 is sent.\n

\n\n \n\n

People search

\n\n \n

\n Search through all the people in our database, using the same mechanism as described for show searches.\n

\n\n \n\n

Schedule

\n\n

\n The schedule is a complete list of episodes that air in a given country on a given date. Episodes are returned in the order\n in which they are aired, and full information about the episode and the corresponding show is included.\n

\n\n

\n This endpoint will only return episodes that are tied to a specific country, either via a Network or via a local Web Channel\n such as HBO Max or Sky Go. Episodes from global Web Channels like Netflix are not included.\n

\n\n

\n Note that contrary to what you might expect, the ISO country code for the United Kingdom is not UK, but GB.\n

\n\n \n\n

Web/streaming schedule

\n\n

\n The web schedule is a complete list of episodes that air on web/streaming channels on a given date. TVmaze distinguishes between local and global\n Web Channels: local Web Channels are only available in one specific country, while global Web Channels are available in multiple countries. To query\n both local and global Web Channels, leave out the country parameter. To query only local Web Channels, set country to an ISO country\n code. And to query only global Web Channels, set country to an empty string.\n

\n\n \n\n

Full schedule

\n\n

\n The full schedule is a list of all future episodes known to TVmaze, regardless of their country. Be advised\n that this endpoint's response is at least several MB large. As opposed to the other endpoints, results are cached for 24 hours.\n

\n\n \n\n

Shows

\n\n

Show main information

\n\n

\n Retrieve all primary information for a given show. This endpoint allows embedding of additional information. See the section\n embedding for more information.\n

\n\n \n\n

Show episode list

\n\n

\n A complete list of episodes for the given show. Episodes are returned in their airing order, and include full episode information.\n By default, specials are not included in the list.\n

\n\n \n\n

Show alternate lists

\n\n

\n Alternate episode lists for this show, for example DVD ordering. For a description of the different types of alternate lists\n that you can find, please refer to the alternate episode policy.\n

\n\n \n\n \n\n \n\n

Episode by number

\n\n

\n Retrieve one specific episode from this show given its season number and episode number. This either returns the full information\n for one episode, or a HTTP 404.\n

\n\n \n\n

Episodes by date

\n\n

\n Retrieve all episodes from this show that have aired on a specific date. This either returns an array of full episode info,\n or a HTTP 404. Useful for daily (talk) shows that don't adhere to a common season numbering.\n

\n\n \n\n

Show seasons

\n\n

\n A complete list of seasons for the given show. Seasons are returned in ascending order and contain the full information\n that's known about them.\n

\n\n \n\n
Season episodes
\n\n

\n A list of episodes in this season. Specials are always included in this list. This endpoint allows embedding of additional information.\n

\n\n \n\n

Show cast

\n\n \n

\n A list of main cast for a show. Each cast item is a combination of a person and a character. Items are ordered by importance, which\n is determined by the total number of appearances of the given character in this show.\n

\n\n \n\n

Show crew

\n\n \n

\n A list of main crew for a show. Each crew item is a combination of a person and their crew type.\n

\n\n \n\n

Show AKA's

\n\n \n

\n A list of AKA's (aliases) for a show. An AKA with its country set to null indicates an AKA in the show's original country. Otherwise,\n it's the AKA for that show in the given foreign country.\n

\n\n \n\n

Show images

\n\n \n

\n A list of all images available for this show. The image type can be \"poster\", \"banner\", \"background\", \"typography\", or NULL in case of legacy\n unclassified images. For a definition of these types, please refer to the main image and\n general image policies.\n

\n\n

\n All image types are available under the \"original\" resolution; posters and banners are also available as a smaller resized version (\"medium\").\n

\n\n \n\n

Show index

\n\n

\n A list of all shows in our database, with all primary information included. You can use this endpoint for example if you want to build\n a local cache of all shows contained in the TVmaze database. This endpoint is paginated, with a maximum of 250 results per page. The\n pagination is based on show ID, e.g. page 0 will contain shows with IDs between 0 and 250. This means a single page might contain less\n than 250 results, in case of deletions, but it also guarantees that deletions won't cause shuffling in the page numbering for other shows.\n

\n\n

\n Because of this, you can implement a daily/weekly sync simply by starting at the page number where you last left off, and be sure\n you won't skip over any entries. For example, if the last show in your local cache has an ID of 1800, you would start the re-sync at page number\n floor(1800/250) = 7. After this, simply increment the page number by 1 until you receive a HTTP 404 response code, which\n indicates that you've reached the end of the list.\n

\n\n

\n As opposed to the other endpoints, results from the show index are cached for up to 24 hours.\n

\n\n \n\n

Episodes

\n\n

Episode main information

\n\n

\n Retrieve all primary information for a given episode. This endpoint allows embedding of additional information. See the section\n embedding for more information.\n

\n\n \n\n

Episode guest cast

\n\n

\n Retrieve all guest cast starring in an episode.\n

\n\n \n\n

Episode guest crew

\n\n

\n Retrieve all guest crew working on an episode.\n

\n\n \n\n

People

\n\n

Person main information

\n\n

\n Retrieve all primary information for a given person. This endpoint allows embedding of additional information. See the section\n embedding for more information.\n

\n\n \n\n

Person cast credits

\n\n

\n Retrieve all (show-level) cast credits for a person. A cast credit is a combination of both a show and a character. By\n default, only a reference to each show and character will be returned. However, this endpoint supports embedding, which\n means full information for the shows and characters can be included.\n

\n\n \n\n

Person crew credits

\n\n

\n Retrieve all (show-level) crew credits for a person. A crew credit is combination of both a show and a crew type. By\n default, only a reference to each show will be returned. However, this endpoint supports embedding, which\n means full information for the shows can be included.\n

\n\n \n\n

Person guest cast credits

\n\n

\n Retrieve all (episode-level) guest cast credits for a person. A guest cast credit is a combination of both an episode and a character. By\n default, only a reference to each episode and character will be returned. However, this endpoint supports embedding, which\n means full information for the episodes and characters can be included.\n

\n\n \n\n

Person index

\n\n

\n Like the show index but for people; please refer to the show index documentation. A maximum of 1000 results per page is returned.\n\n

\n\n

Updates

\n\n

Show updates

\n\n

\n A list of all shows in the TVmaze database and the timestamp when they were last updated. Updating a direct or indirect\n child of a show will also mark the show itself as updated. For example; creating, deleting or updating an episode or\n an episode's gallery item will mark the episode's show as updated. It's possible to filter the resultset to only include\n shows that have been updated in the past day (24 hours), week, or month.\n

\n\n \n\n

Person updates

\n\n

\n Like the show updates endpoint, but for people. A person is considered to be updated when any\n of their attributes are changed, but also when a cast- or crew-credit that involves them is created or deleted.\n

\n\n \n\n

Embedding

\n\n

\n As defined by the HAL convention, our API resources can contain\n links to related URLs. These URLs can refer to either a collection (like a list of episodes), or to an individual\n resource (like an episode). References to an individual resource are always advertised in the model's _links, for\n example as a show's _links.previousepisode or a cast credit's _links.character. References to\n collections are not actively advertised in the _links output, but are documented here. Both types of links can be\n embedded in the response by using the embed query parameter.\n

\n

\n For example, \n https://api.tvmaze.com/shows/1?embed=episodes will serve the show's main information and its episode list in one single\n response. https://api.tvmaze.com/shows/1?embed=nextepisode would\n embed the details of that show's upcoming episode in the response, but only if one such episode currently exists. Embedding\n multiple links is possible with the array syntax: \n https://api.tvmaze.com/shows/1?embed[]=episodes&embed[]=cast\n

\n\n

Images

\n\n

\n Most resources available in the API have an image property that refers to that item's primary image. For shows, people\n and characters this is an image in poster format; for episodes the image is in landscape format. If an image exists, the\n image property will be a dictionary containing a \"medium\" and \"original\" key, referring to the image in fixed resized\n dimensions or in the original uploaded resolution. If no image exists yet, the image property will be NULL.\n

\n\n

\n You are free to directly link (\"hotlink\") to our image CDN. However, for performance reasons we recommend to cache\n the images on your end: on your own server in case of a web application, or on the client in case of a desktop/mobile app.\n Images can safely be cached indefinitely: on our end the content of a specific image URL will never change; if an item's\n primary image changes, the item's image URL will change instead.\n

\n\n

HTTPS

\n\n

\n All endpoints and links embedded in the API response - to other API endpoints or to our image CDN - are HTTPS by default,\n but it's possible to access them over unencrypted HTTP as well.\n

\n \n

Caching

\n\n

\n All output is cached by our HTTP load balancers for 60 minutes, so when information is updated on the site, please\n allow up to 1 hour for the changes to propagate to the API.\n

\n\n

Rate limiting

\n\n

\n API calls are rate limited to allow at least 20 calls every 10 seconds per IP address. If you exceed\n this rate, you might receive an HTTP 429 error. We say at least, because rate limiting takes place on the\n backend but not on the edge cache. So if your client is only requesting common/popular endpoints like shows\n or episodes (as opposed to more unique endpoints like searches or embedding), you're likely to never hit\n the limit. For an optimal throughput, simply let your client back off for a few seconds when it receives a 429.\n

\n\n

\n Under special circumstances we may temporarily have to impose a stricter rate limit. So even if your client\n wouldn't normally exceed our rate limit, it's useful to gracefully handle HTTP 429 responses: simply retry\n the request after a small pause instead of treating it as a permanent failure.\n

\n\n

\n Additionally, you should ensure that HTTP connections are not unnecessarily left open. Either explicitly close\n the HTTP connection after every request, re-use connections for subsequent requests, or make use of HTTP2 multiplexing.\n Leaving more than 1 connection to our servers idle may result in your IP getting blocked.\n

\n\n

\n While not required, we strongly recommend setting your client's HTTP User Agent to something that'll uniquely\n describe it. This allows us to identify your application in case of problems, or to proactively reach out\n to you.\n

\n\n

CORS

\n\n

\n All endpoints are CORS (Cross-origin resource sharing)\n enabled, which means our API can be used directly in web applications without having to resort to JSONP or HTTP proxying.\n

\n\n

Licensing

\n\n

\n Use of the TVmaze API is licensed by CC BY-SA. This means\n the data can freely be used for any purpose, as long as TVmaze is properly credited as source and your usage\n complies with the ShareAlike provision. You can satisfy the attribution requirement by linking\n back to TVmaze from within your application or website, for example using the URLs available in the API.\n\n

Enterprise API

\n\n

\n Does your usecase require data or functionality not available in the public API? Are you looking for a different license,\n SLA or support level? Contact our sales department to discuss the possibilities.\n

\n
\n
\n
\n\n\n
\n
\n \n
\n\n \n\n
\n\n \n\n\n\n\n\n\n\n\n\n \n\n \n\n \n\n \n \n\n"