Adult Video API Quick Start: Browse, Filter and Paginate Like a Pro

Almost every page on a tube site is a filtered list: a category page, a tag page, a performer page, search results. With an API they are all the same request with different parameters. Here is how to use them well.

The filters

• categories — e.g. amateur,milf
• tags — e.g. blonde,outdoor
• performers — performer slugs
• studios — studio slugs
• search — full-text over title and description
• sort — views, likes, published or trending

Comma-separated values inside one parameter widen the match; combining different parameters narrows it. A "blonde amateur" page is simply categories=amateur&tags=blonde.

Pagination

Responses include count, next and previous. Use page_size up to 100. Two habits keep things smooth:

1. Follow next instead of building page URLs yourself — the server already knows the right query.
2. Do not walk thousands of pages on every request. For a full import, page through once and then switch to the changelog for updates.

Edge caching works in your favour

Identical browse requests are cached at the edge for a short window. Use stable parameter order and the same page_size everywhere, and your own traffic spikes turn into cache hits instead of slow queries.

Building pages from it

# category page
/api/database/browse/?categories=amateur&sort=published&page=1
# performer page
/api/database/browse/?performers=some-performer&sort=views
# search box
/api/database/browse/?search=hotel%20room&page_size=24

The metadata endpoint lists the available categories, tags, performers and studios, so you can generate navigation menus and sitemaps from the same source of truth instead of hard-coding them.

Respect the limits

Each key has per-minute and per-day request limits that comfortably cover a site sync. If you hit them, you are almost always re-fetching data you could cache. If you genuinely need more, tell us what you are building and we will raise them.