Skip to content

Adult Content Feeds · Editorial review

RedTube API review: twenty tagged videos per call

redtube.com

RedTube API returns twenty videos per call, with no account and no key, each with its tags and player address. Separate lists give 111 categories and 23,480 performers. One of the nine methods returns an error.

Our verdict on RedTube API

RedTube API suits a tube that wants videos already sorted by category, tag and performer, played in RedTube’s embedded player. Building a large index takes many calls, at twenty videos each.

RedTube interface documentation listing the available methods
RedTube API

The nine RedTube API methods

Everything goes through one address with the method name as a parameter, in JSON or XML, with no account and no key. searchVideos returns twenty videos, filtered by category, tag, performer, ordering or period. getVideoById returns thirteen fields, including tags, the embed address and the publish date. isVideoActive answers true or false, and getDeletedVideos pages through 12,230,870 removed IDs. Three list methods return 111 categories, 1,000 tags and 23,480 performers, and a fourth adds performer details.

getVideoEmbedCode answers “No video with this ID” with code 2002, even for an ID that isVideoActive reports as active. The embed_url field from the search does the same job. Errors carry documented codes, such as 3001 when no category is found.

The search caps

An unfiltered search reports 300,000 results, and a keyword search 200,000, whatever the keyword. These figures are caps. A category gives a true count, 218,924 for Anal for example, and can be paged to the end.

RedTube API strengths and limitations

Strengths

  • Tags in every response.
  • Performer lists included.
  • Documented error codes for scripts.

Limitations

  • Twenty videos per call.
  • A broken method for embed code.
  • Search counts capped.

RedTube API versus Eporner API

Eporner API returns up to 1,000 videos per call and publishes a daily CSV of its whole catalogue. RedTube returns twenty per call but puts tags and performer lists in the interface itself.

Sources