AniList Trending Scraper

Export the current **AniList anime trend list** as clean JSON, CSV or Excel rows without maintaining a GraphQL client. The Actor queries AniList first, keeps the default run small, and stores one normalized record per default-dataset item. If AniList temporarily disables GraphQL, it uses Kitsu's trending feed and accepts only records that Kitsu maps back to a verified AniList anime ID.

The Actor is production-oriented rather than a demo. It includes bounded inputs, retries for transient service errors, explicit empty-result failures, a structured dataset view and source links that make each row traceable. Run it manually, call it through the Apify API, schedule it, or connect it to Make, Zapier and n8n.

## What this Actor returns

Collect AniList trending records and export id, averagescore, romaji, english, source, scraped at as structured JSON, CSV or Excel data.

Core output fields include:

- `id` (AniList anime ID)

• averagescore

• romaji

• english

• trend_source

• score_source

• anilist_url

• source

• scraped_at

  Additional source and search fields may be included when they improve traceability. Fields that are not available for a particular record are returned as null rather than guessed.

  Why use this data source?

  AniList normally exposes its trend ranking through the public GraphQL endpoint. The Actor queries that endpoint first and preserves each AniList ID plus its canonical page URL.

  AniList has occasionally returned HTTP 403 with a message that the API was disabled for stability work. During that outage, the Actor reads Kitsu's public trending feed, fetches Kitsu's mapping records in one batch, and drops any row without an anilist/anime mapping. Fallback rows state Kitsu trending fallback in trend_source and Kitsu averageRating in score_source; the Actor doesn't present Kitsu's rank or score as AniList data.

  Common use cases

  Search and export AniList trending records without manual copying

The structured output makes this workflow repeatable: run it on demand, schedule it, or pass the rows to the next system without manually copying records. Keep the input narrow enough to produce relevant results and retain the source identifiers for verification.

Create a scheduled monitor with stable source identifiers

The structured output makes this workflow repeatable: run it on demand, schedule it, or pass the rows to the next system without manually copying records. Keep the input narrow enough to produce relevant results and retain the source identifiers for verification.

Enrich an internal catalogue, dashboard or research workflow

The structured output makes this workflow repeatable: run it on demand, schedule it, or pass the rows to the next system without manually copying records. Keep the input narrow enough to produce relevant results and retain the source identifiers for verification.

Send new records to a spreadsheet, database or automation

The structured output makes this workflow repeatable: run it on demand, schedule it, or pass the rows to the next system without manually copying records. Keep the input narrow enough to produce relevant results and retain the source identifiers for verification.

## Input

| Field | Type | Description |
| --- | --- | --- |
| `maxResults` | `integer` | Maximum records saved to the default dataset. Default: `3`. |

The default `maxResults` is deliberately low so a first run finishes quickly and produces an inexpensive proof dataset. The endpoint exposes the current top 10, so the maximum is `10`.

### Example input

```json
{

"maxResults": 3 } ```

## Output and export formats

Every matching record is pushed separately to the default Apify dataset. From the Dataset tab you can download JSON, CSV, Excel, XML, RSS or JSONL. API clients can use the dataset-items URL returned by the run object. Because the schema is stable, the output can be loaded into a database, spreadsheet, data warehouse or agent workflow without scraping log text.

A representative row contains the AniList ID, romaji and English titles, average score, source labels, AniList page URL and collection timestamp. During fallback runs, `fallback_record_url` links to the Kitsu API record used for the row.

## How it works

1. The Actor validates and bounds the supplied input.
2. It calls AniList GraphQL with a descriptive request identity.
3. Transient timeouts, rate limits and server errors are retried with backoff.
4. If GraphQL is unavailable, it reads Kitsu trending and verifies every AniList ID through Kitsu's mapping relationship.
5. Source fields make the ranking and score origin explicit before each row reaches the default dataset.
6. A zero-row response fails clearly instead of reporting a misleading successful run.

The Actor runs with limited permissions and only requests permission to write its result dataset. It does not require access to your other Actors, key-value stores or account resources.

## Scheduling and automation

Create an Apify Schedule to run the Actor hourly, daily or weekly. A schedule is useful for monitoring fresh records, while a one-off run is better for research or backfills. Keep inputs in the Task rather than hard-coding them in an external workflow so they can be reviewed and changed safely.

In Make, Zapier or n8n, use the Apify integration to run this Actor and then iterate over default-dataset items. For custom code, call `POST /v2/acts/benthepythondev~anilist-trending-scraper/runs`, poll the run to a terminal state, and fetch items from the run's default dataset. Never place an Apify token in a public frontend.

## Pricing

This Actor uses pay-per-event pricing: `$0.00005` when a run starts and `$0.0025` for each record written to the default dataset. A full 10-row run has a result charge of about `$0.025`, plus the small start event and normal Apify platform usage.

## Data quality and responsible use

Upstream records can change or be incomplete. AniList and Kitsu calculate trends independently, so fallback ordering isn't an AniList ranking. Check `trend_source` and `score_source` before comparing runs, and verify the mapped ID on the linked AniList page.

Public does not mean context-free. Preserve attribution and source URLs, respect intellectual-property and privacy obligations, and do not use the data for prohibited discrimination, harassment or unsolicited bulk messaging. If a record drives a legal, financial, safety or compliance decision, verify it with the authoritative publisher and a qualified professional.

The upstream service can add fields, revise records, enforce quotas or experience downtime. The Actor retries transient failures, but it cannot guarantee that the source is always available or that every upstream record is complete. Scheduled users should monitor failed runs and retain the source ID so changed rows can be reconciled.

## FAQ

### Do I need an account or API key?

The default workflow uses a public, supported interface and does not require a user login. If the publisher changes its access policy in the future, the Actor will fail clearly rather than collecting data through an unrelated account.

### Can I export the results to CSV or Excel?

Yes. Open the default dataset after a run and select the desired download format. JSON and JSONL are best for code, while CSV and Excel are convenient for review and enrichment.

### Can I run it on a schedule?

Yes. Save a Task with the filters you want, then attach an Apify Schedule. Start with a daily run and adjust only after observing result volume, change frequency and cost.

### How are duplicates handled?

The Actor returns records supplied by the source for the requested query. Where the source exposes stable identifiers, those identifiers are included so downstream systems can upsert instead of append. Some sources intentionally publish several rows for one broader case or process; the README limitations explain those situations.

### Why did my run return no rows?

AniList and Kitsu may both be unavailable, or Kitsu may not publish an AniList mapping for a trending record. Review the run log and retry with `maxResults` set to `3` before reporting the run ID through the Actor page.

### Is this an official product of the source publisher?

No. This is an independent Apify Actor that reads a public interface and links back to the authoritative source. Source names are used only to describe compatibility.

### How do I get support?

Open an issue on the Actor page with the run ID, a redacted input example and the field you expected. Do not post API tokens, personal credentials or private feed URLs in a public issue.

## You might also like

- [pypi-scraper](https://apify.com/benthepythondev/pypi-scraper)

• maven-central-scraper

• dockerhub-scraper

  If the Actor produced a useful dataset, please leave a short Apify Store review. Reviews help prioritize maintenance and show other users which workflows are working in production.

  Keywords: anilist trending scraper, anilist trending, data API, public data scraper, Apify Actor, automation, structured dataset, JSON export, CSV export, scheduled monitoring, market research, business intelligence.