# Google Trends Scraper - Trends API & Trending Now (`eiv/google-trends-scraper`) Actor

Google Trends API without a browser: interest over time, interest by country, state, US metro or city, top and rising related queries, comparisons of up to 5 terms, YouTube/News/Shopping search, and Trending now searches with volume and news. Fast, no login, pay per keyword.

- **URL**: https://apify.com/eiv/google-trends-scraper.md
- **Developed by:** [Eimantas V](https://apify.com/eiv) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.30 / 1,000 keyword trends

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

**Google Trends Scraper** turns any keyword into Google Trends data: interest over time, interest by country, state, US metro area or city, top and rising related queries, and comparisons of up to 5 terms, plus today's **Trending now** searches with search volume and news. Paste keywords, topic IDs or Google Trends URLs and get one clean row per search. No login, no API key, no browser, from **$1.30 per 1,000 keywords**.

```json
{
  "searchTerm": "air fryer",
  "geoName": "United States",
  "timeRange": "today 12-m",
  "averageInterest": 65,
  "latestInterest": 56,
  "peakInterest": 100,
  "peakDate": "2026-04-12T00:00:00.000Z",
  "trendChangePercent": 5.4,
  "trendDirection": "stable",
  "topQuery": "air fryer chicken",
  "topRisingQuery": "laptop stand",
  "interestOverTime": [{ "date": "2026-09-27T00:00:00.000Z", "interest": 56, "isPartial": false, "label": "Sep 27 - Oct 3, 2026" }, "... 53 weekly points"],
  "interestByRegion": [{ "regionCode": "US-WY", "regionName": "Wyoming", "interest": 100 }, "... 51 states"],
  "relatedQueriesRising": [{ "query": "laptop stand", "formattedValue": "Breakout", "isBreakout": true }, "... 25 queries"]
}
```

**60 keywords with their full timeline, 51 states and 50 related queries each in 33 seconds on default settings; 300 keyword-country searches in 2.5 minutes. Every one of them succeeded.**

### What does Google Trends Scraper do?

It reads the same data the Google Trends website shows, through the JSON endpoints the website itself uses, and writes it as one row per search. Every row has the full data and ready-made summary columns (average, latest and peak interest, trend change in percent, top region, top and rising query), so a spreadsheet of 500 keywords can be sorted by momentum without any formulas.

- **Any search Google Trends can do.** Keywords, Knowledge Graph topics (`/m/02vqfm` = Coffee, the drink, in every language), comparisons of up to 5 terms on one scale, any location (worldwide, 250 countries, regions, US metro areas), any time range from the past hour to 2004-present or custom dates, 1,100+ categories, and web, image, News, Google Shopping or YouTube search.
- **Many locations at once.** Put `US, GB, DE, IN, BR` in Location and every keyword is measured in each country, one row each.
- **Trending now.** What is trending on Google in any country right now, or in the past 4 hours to 7 days: search volume, growth, when it started, whether it is still active, category, the searches grouped into the trend, and news articles.
- **Paste Google Trends URLs.** Copy the address of any Explore or Trending now page from your browser; its location, dates, category and search type are kept.
- **Only pay for results.** Searches Google has not enough data for, invalid locations and failed requests return an error row and are never charged.
- **Built for automation and AI agents.** Run it on a schedule, call it from the API, connect it to Make, Zapier, n8n or Google Sheets, or let an AI agent call it through Apify's MCP server.

### Why it is fast and reliable

Most Google Trends scrapers open the website in a browser and wait for every chart to render, which is slow and breaks whenever Google rate-limits the browser. This Actor asks Google Trends' own JSON endpoints directly, the way the page loads its charts: one request per section, a few kilobytes each, no rendering. Google rate-limits busy addresses, so requests are spread over a pool of addresses, a rate-limited address is rested and the request moves to another one. One unlucky address never fails a search.

### What data can you extract from Google Trends?

| Field | Example | What it is |
|---|---|---|
| `searchTerm` | `coffee, tea` | The term, or the compared terms; topic IDs show as their name |
| `geoName` / `geo` | `United States` / `US` | Location of the search (`null` code = worldwide) |
| `timeRange`, `startDate`, `endDate`, `interval` | `today 12-m`, `WEEK` | The period and the spacing of its points |
| `averageInterest` | `65` | Mean interest (0-100) of the first term over the period |
| `latestInterest`, `latestDate` | `56` | Interest at the last complete point |
| `peakInterest`, `peakDate` | `100`, `2026-04-12` | When the term peaked |
| `trendChangePercent`, `trendDirection` | `5.4`, `stable` | Last quarter of the period against the first: rising, falling, stable or new |
| `topRegion`, `topQuery`, `topRisingQuery` | `Wyoming`, `air fryer chicken` | The headline of each section |
| `interestOverTime` | 53 points | Every point: date, interest of each term, partial flag |
| `interestByRegion` | 51 regions | Interest by region, highest first; for a comparison, each term's share |
| `relatedQueriesTop` / `relatedQueriesRising` | 25 + 25 per term | Related searches with popularity or growth (Breakout = over 5,000 %) |
| `termSummaries` | one per term | Average, latest, peak and trend for every compared term |
| `topics` | `Coffee (Beverage) /m/02vqfm` | Knowledge Graph topics for each term (optional) |
| `trend`, `searchVolume`, `increasePercent` | `freddie jackson`, `200000`, `1000` | Trending now rows: the search, its volume (200K+) and growth |
| `startedAt`, `endedAt`, `isActive`, `hoursActive` | `2026-10-06T14:10Z` | When the trend started and whether it is still active |
| `categories`, `relatedQueries`, `newsArticles` | `Sports` | The trend's categories, grouped searches and news (title, link, source, image) |
| `trendsUrl` | `https://trends.google.com/...` | The same search on Google Trends |

### How to scrape Google Trends

1. Click **Try for free** and type your keywords into **Search terms**, one per line. Write `coffee, tea, matcha` on one line to compare them.
2. Choose a **Location** (empty = worldwide, or `US`, or several: `US, GB, DE`) and a **Time range**.
3. Optional: add countries under **Trending now** to get today's trending searches too.
4. Click **Start**. A few keywords take seconds; 300 searches take about 2.5 minutes. Open the **Output** tab or download JSON, CSV, Excel or HTML.

### How much does it cost to scrape Google Trends?

You pay per row, and the price drops on higher Apify plans:

| Apify plan | Per 1,000 keywords | Per 1,000 trending searches |
|---|---|---|
| Free | $2.50 | $1.00 |
| Starter | $2.00 | $0.80 |
| Scale | $1.70 | $0.60 |
| Business | $1.30 | $0.50 |

A keyword row is one search: one term or a comparison of up to 5, in one location, with every section you selected.

- **100 keywords in the US on the Starter plan:** 100 rows x $0.002 = **$0.20**.
- **50 keywords in 5 countries, plus the top 50 trending searches in each of those countries, on the Business plan:** 250 x $0.0013 + 250 x $0.0005 = **$0.45**.
- A run also costs **$0.00005** to start. Searches without enough data, invalid locations and failed requests cost nothing.
- The Free plan's $5 monthly credit covers about **2,000 keyword searches**.

### Input

```json
{
  "searchTerms": ["air fryer", "coffee, tea, matcha", "/m/02vqfm", "https://trends.google.com/trends/explore?q=minecraft&geo=GB&gprop=youtube"],
  "geo": "US, GB",
  "timeRange": "today 12-m",
  "category": "",
  "searchType": "web",
  "includeInterestByRegion": true,
  "regionResolution": "auto",
  "includeRelatedQueries": true,
  "trendingCountries": ["US"],
  "trendingHours": "24",
  "maxTrendingPerCountry": 50,
  "maxItems": 1000
}
```

| Field | Default | Notes |
|---|---|---|
| Search terms | `coffee`, `chatgpt, gemini` (example) | Keywords, comparisons (comma-separated, up to 5), topic IDs or Google Trends URLs, one per line |
| Google Trends URLs | none | The same, in the URL-list shape other Actors output |
| Google Sheet with search terms | none | ID or link of a public sheet; terms from its first column |
| Location | worldwide | `US`, `US-CA`, `US-NY-501`, or several: `US, GB, DE` (one row per location) |
| Time range | Past 12 months | Past hour, 4 hours, day, 7 days, 30 days, 90 days, 12 months, 5 years, 2004-present |
| Custom time range | none | `2024-01-01 2024-12-31`, or hours within the past week: `2026-10-01T05 2026-10-02T17` |
| Category / Category ID | All categories | 25 main categories, or any of 1,100+ IDs (916 = Coffee & Tea) |
| Search type | Web search | Image search, News, Google Shopping or YouTube |
| Language | English (US) | Language of region names, topic names and labels |
| Include the full timeline | on | Off keeps rows small; the summary columns stay |
| Interest by region / Region level | on / auto | Countries, regions, US metro areas or cities |
| Related queries | on | Top and rising, 25 each per term |
| Topic suggestions | off | Knowledge Graph topics for each term (one extra request per term) |
| Trending now: countries | none | `US`, `GB`, `DE`, `US-CA`: one row per trending search |
| Trending window, category, sort, active only | 24 hours, all, relevance, off | Filters for Trending now |
| News articles per trend | 0 | Up to 10 per trend |
| Max trending searches per country | 50 | The US often has 400+ a day |
| Max results | 1,000 | Total rows: your cost cap |

Inputs written for other Google Trends Actors work as they are: `searchTerms`, `startUrls`, `timeRange`, `customTimeRange`, `geo`, `category`, `spreadsheetId`, `maxItems`, and `keyword` / `timeframe`.

### Output

Each search is one row. The **Keyword trends** view shows the summary columns; **Interest over time**, **Interest by region**, **Rising queries** and **Top queries** show one row per point, region or query, ready for charts and pivot tables; **Trending now** shows the trending searches. Every export includes all fields.

```json
{
  "recordType": "trending",
  "trend": "argentina vs benin",
  "rank": 1,
  "geo": "US",
  "geoName": "United States",
  "searchVolume": 1000000,
  "searchVolumeText": "1M+",
  "increasePercent": 1000,
  "startedAt": "2026-10-05T19:20:00.000Z",
  "endedAt": null,
  "isActive": true,
  "hoursActive": 42.3,
  "categories": ["Sports"],
  "relatedQueries": ["argentina vs benin", "argentina - benín", "messi", "messi last game"],
  "newsArticles": [
    {
      "title": "Lionel Messi's final Argentina match was an emotional send-off worthy of a legend",
      "url": "https://www.espn.com/soccer/story/_/id/50123513/lionel-messi-final-argentina-match-emotional-sendoff-worthy-legend",
      "source": "ESPN",
      "publishedAt": "2026-10-07T08:37:00.000Z",
      "imageUrl": "https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcT7yG299UyB1vd5A4F4RP-eIoVBeLY8nyYlvLBKEY8s9LKHyCIMAUIWrUiFr74"
    }
  ],
  "trendsUrl": "https://trends.google.com/trends/explore?q=argentina%20vs%20benin&date=now%207-d&geo=US&hl=en-GB",
  "windowHours": 48
}
```

A search that returns nothing becomes a row with `"recordType": "error"` and an `errorCode` instead of failing the run:

| `errorCode` | Meaning |
|---|---|
| `NO_DATA` | Google Trends has not enough search volume for this search (its "not enough data" answer). Try a longer period, a larger location or a broader term |
| `INVALID_INPUT` | A location code, time range or category Google Trends does not accept |
| `RATE_LIMITED` / `BLOCKED` | Google Trends refused every address the Actor tried; run it again later |
| `PARSE_FAILED` | Google changed its answer format; please report it |

Error rows are never charged.

### Tips and limits

- **Interest is relative, not a search count.** Google Trends scales every search to 0-100, where 100 is the highest point of that search. Values from two separate rows are not comparable; put the terms on one line (`coffee, tea`) to compare them on one scale. Trending now rows do carry absolute search volume.
- **Google samples its data.** The same search can differ by a few points from one day to the next, and small locations (a small state, a city) are noisier than large ones. This is how Google Trends works, in the browser too.
- **Related topics are not included.** Google returns an empty related-topics list to automated clients, browser-based scrapers included (checked October 2026). Related queries, and topic suggestions for each term, are included.
- **Up to 5 terms per comparison, hourly ranges within the past 7 days, metro areas for the US only.** These are Google Trends' own limits; a metro request outside the US falls back to regions.
- **Faster runs:** turn off sections you do not need (each is one request per search); keep Concurrency at 5 unless your run is large.
- **Hit your spending limit?** The run stops cleanly at your maximum cost per run and keeps everything it collected. Raise the limit in the run options to get more.

### FAQ

#### Is it legal to scrape Google Trends?

This Actor collects only aggregated, anonymous data that Google Trends shows publicly, without logging in: search interest is an index, not personal data. News articles attached to trending searches are public headlines and links. Use the data in line with Google's terms and your local law, and ask a lawyer if you are unsure. Google Trends is a trademark of Google LLC; this Actor is not affiliated with or endorsed by Google.

#### Is there an official Google Trends API?

Google announced an official Trends API in 2025 with access limited to approved testers. This Actor works today for any keyword, without keys, approval or a Google Cloud project, and returns the same sections as the website plus Trending now.

#### Can I use it through the API or with Make, Zapier and n8n?

Yes. Every run can be started through the [Apify API](https://docs.apify.com/api/v2) and returns the dataset as JSON, CSV or Excel. Schedules, webhooks and integrations for Make, Zapier, n8n and Google Sheets are on the **Integrations** tab. Schedule it daily with Trending now countries to keep a history of what trended.

#### Can AI agents use it?

Yes. Agents connected to [Apify's MCP server](https://mcp.apify.com) can find and run this Actor as a tool, with the same per-row pricing. Ask an agent "Is interest in heat pumps rising in Germany?" or "What is trending in the UK right now?" and it can answer from live Google Trends data.

#### Why did I get fewer rows than I asked for?

A search without enough data returns an error row (`NO_DATA`) instead of a result; the run may also have reached Max results, your maximum cost per run, or its timeout. The log says which, and nothing collected before that is lost.

### Related scrapers

- [Google Search Results Scraper](https://apify.com/eiv/google-search-scraper): the pages that rank for your keywords, with People Also Ask and AI Overviews.
- [Keyword Research Scraper](https://apify.com/eiv/keyword-research-scraper): hundreds of real keyword ideas from Google, YouTube and Amazon autocomplete, to feed into Google Trends.
- [YouTube Search Scraper](https://apify.com/eiv/youtube-search-scraper): the videos behind a trending YouTube search.
- [News & Brand Monitoring Scraper](https://apify.com/eiv/news-monitoring-scraper): the news coverage behind a trend.

### Support

Missing a field, or found a search that does not work? Open an issue on the **Issues** tab with the input you used, and it will be looked at quickly.

# Actor input Schema

## `searchTerms` (type: `array`):

One search per line. A keyword (coffee), several separated by commas to compare them on one scale (coffee, tea, matcha - up to 5), a topic ID (/m/02vqfm), or a Google Trends URL copied from your browser (it keeps its own location, dates and category). Each line returns one row per location.

## `startUrls` (type: `array`):

Google Trends Explore or Trending now URLs, in the URL-list shape other Actors output, so a previous Actor's results can be fed straight in. Same as pasting the URLs into Search terms.

## `spreadsheetId` (type: `string`):

Optional. The ID or link of a public Google Sheet (shared as "Anyone with the link can view"). Search terms are read from its first column; row 1 is the header. A cell can hold a comparison: coffee, tea.

## `geo` (type: `string`):

Where the searches come from. Empty = worldwide. A country (US, GB, DE), a region (US-CA, GB-ENG) or a US metro area (US-NY-501). Several separated by commas (US, GB, DE) give one row per location for every search term.

## `timeRange` (type: `string`):

The period to analyse. Shorter ranges give finer points: past hour and 4 hours by the minute, past day every 8 minutes, past 7 days hourly, up to 90 days daily, 12 months and 5 years weekly, since 2004 monthly.

## `customTimeRange` (type: `string`):

Optional, overrides Time range. Dates as "YYYY-MM-DD YYYY-MM-DD" (e.g. 2024-01-01 2024-12-31, from 2004 on), or hours as "YYYY-MM-DDTHH YYYY-MM-DDTHH" (UTC, within the past 7 days).

## `category` (type: `string`):

Limit the searches to one category, e.g. "jaguar" in Autos & Vehicles means the car. For a sub-category use Category ID below, or paste a Google Trends URL with cat= in Search terms.

## `categoryId` (type: `integer`):

Optional, overrides Category: any of Google Trends' 1,100+ category IDs, e.g. 916 = Coffee & Tea, 390 = Mobile Phones. Find one in a Google Trends URL (cat=916).

## `searchType` (type: `string`):

Which Google search to measure: web search, image search, Google News, Google Shopping or YouTube search.

## `language` (type: `string`):

Language of region names, topic names and date labels. Does not change which searches are counted.

## `includeInterestOverTime` (type: `boolean`):

Every point of interest over time (0-100) in each row. Off keeps rows small; the summary columns (average, latest, peak, trend change) are filled either way.

## `includeInterestByRegion` (type: `boolean`):

Where the term is most popular (0-100 per region; for a comparison, each term's share of the region). Adds one request per search.

## `regionResolution` (type: `string`):

Level of the region breakdown. Auto = Google's choice (countries for worldwide, states or regions for a country). Metro areas exist for the US only.

## `includeLowVolumeRegions` (type: `boolean`):

Also list regions with little search volume, as Google's "Include low search volume regions" checkbox does.

## `includeRelatedQueries` (type: `boolean`):

Top and rising searches related to each term (25 each), with Breakout flags for queries up more than 5,000 %. Adds one request per term.

## `includeTopics` (type: `boolean`):

Google's Knowledge Graph topics for each term (e.g. coffee -> Coffee, Beverage, /m/02vqfm). Search a topic ID to count every spelling and language of it. Adds one request per distinct term.

## `trendingCountries` (type: `array`):

Get what is trending on Google right now, one row per trending search, with search volume, growth, start time, category and related searches. One country or region code per line: US, GB, DE, US-CA.

## `trendingHours` (type: `string`):

Trends that started within this window.

## `trendingCategory` (type: `string`):

Only trends in this category.

## `trendingSort` (type: `string`):

Order of the trends before the per-country limit is applied: Google's relevance order, highest search volume first, or newest first.

## `trendingActiveOnly` (type: `boolean`):

Skip trends Google marks as ended.

## `trendingNewsPerTrend` (type: `integer`):

How many news articles (title, link, source, time, image) to attach to each trending search. 0 = none.

## `maxTrendingPerCountry` (type: `integer`):

Trending now rows per country, after filters and sorting. The US often has 400+ trends a day.

## `maxItems` (type: `integer`):

Stop after this many rows in total (keyword rows plus trending searches). You pay per row, so this is also your cost cap for the run.

## `proxyConfiguration` (type: `object`):

Leave off. The Actor uses Apify's own addresses and moves to Apify datacenter proxies by itself when Google Trends rate-limits one. Set a proxy only if you must use your own; results do not depend on the address.

## `maxConcurrency` (type: `integer`):

How many searches run at the same time. Lower it if the log shows rate limits.

## `requestTimeoutSecs` (type: `integer`):

How long to wait for one response before trying another address.

## `maxRetries` (type: `integer`):

Extra attempts, on fresh addresses, for rate-limited or failed requests.

## Actor input object example

```json
{
  "searchTerms": [
    "coffee",
    "chatgpt, gemini"
  ],
  "geo": "",
  "timeRange": "today 12-m",
  "category": "",
  "searchType": "web",
  "language": "en-US",
  "includeInterestOverTime": true,
  "includeInterestByRegion": true,
  "regionResolution": "auto",
  "includeLowVolumeRegions": false,
  "includeRelatedQueries": true,
  "includeTopics": false,
  "trendingHours": "24",
  "trendingCategory": "all",
  "trendingSort": "relevance",
  "trendingActiveOnly": false,
  "trendingNewsPerTrend": 0,
  "maxTrendingPerCountry": 50,
  "maxItems": 1000,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "maxConcurrency": 5,
  "requestTimeoutSecs": 30,
  "maxRetries": 2
}
```

# Actor output Schema

## `results` (type: `string`):

One row per search (recordType "interest"): summary columns, the full timeline, regions and related queries. Plus Trending now rows (recordType "trending") and uncharged error rows (recordType "error").

## `trending` (type: `string`):

Trending now searches (recordType "trending"): volume, growth, start time, categories, related searches.

## `timeline` (type: `string`):

Every timeline point of every search, unwound into rows: ready for charts and spreadsheets.

## `summary` (type: `string`):

Totals for the run: searches, rows, no-data searches, failures, requests and why the run stopped.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchTerms": [
        "coffee",
        "chatgpt, gemini"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("eiv/google-trends-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "searchTerms": [
        "coffee",
        "chatgpt, gemini",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("eiv/google-trends-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchTerms": [
    "coffee",
    "chatgpt, gemini"
  ]
}' |
apify call eiv/google-trends-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,eiv/google-trends-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/XElgStt7x97LNhf3t/builds/yUFBAyY0ozxdcI78D/openapi.json