# Bunjang Scraper: Korea New Listing & Price Alerts (`accountable_eel/bunjang-listing-lookup`) Actor

Bunjang (bunjang.co.kr) scraper by keyword: run a search and get one row per listing, including price, condition code, location, seller hash and link, plus optional alerts for new listings and price drops. No login required. Pay per listing returned; empty searches are free.

- **URL**: https://apify.com/accountable\_eel/bunjang-listing-lookup.md
- **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community)
- **Categories:** E-commerce, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 listing returneds

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

## Bunjang Scraper: Korea New Listing & Price Alerts

Watch a search, get only what's new. This actor runs your search against **Bunjang's own open
search API** (bunjang.co.kr) — one of Korea's two biggest second-hand marketplace apps — and
returns one clean row per listing: title, price, condition, location, and a permanent link. Turn on
monitoring and it becomes a watchlist: new listings and price drops since your last run, charged
per new row, free on quiet days.

### Who it's for

A reseller or arbitrage buyer watching one category (phones, sneakers, electronics) for underpriced
or newly-posted listings wants a live feed of what's actually on Bunjang right now, without
refreshing the search page by hand. A market-research team tracking asking prices, or a Sheets/n8n
workflow that reacts the moment something new is posted, gets the same shape here: paste a list of
search terms, get back a flat row per listing, and pay only for listings actually returned — a
search that finds nothing costs nothing.

Use it alongside `joonggonara-listing-lookup` and `daangn-listing-lookup` — all three Korean
second-hand marketplaces in this catalogue share the same column names (`listingId`, `title`,
`price`, `currency`, `listingStatus`, `postedAt`, `city`, `sellerType`, `sellerHash`, `imageUrl`,
`url`) so their rows merge cleanly into one feed.

### Why this one

- **Monitoring first, not a one-off dump.** Turn on "Only return results that are new, or dropped
  in price" and this actor becomes a watchlist: it remembers every listing ID it has already shown
  you, and only bills you for what's actually new or has dropped in price since the last run. A
  quiet run — nothing new, nothing cheaper — still finishes and costs only the base run fee.
- **No competing monitoring actor.** The current Apify Store leader for Bunjang, `piotrv1001`'s
  scraper, has 22 lifetime users and no monitoring mode. Korea's DIY alert-bot scene (GitHub bots
  posting new Bunjang listings to Discord/Telegram) is the strongest signal of unmet demand found
  anywhere in this catalogue's Asia research.
- **Reads Bunjang's own open JSON API directly.** No HTML scraping, no anti-bot workaround needed —
  `api.bunjang.co.kr` serves plain JSON with real pagination, confirmed live (two consecutive pages
  overlapped on only 1 of 100 listings).
- **Never charged for a miss, or a quiet monitoring run.** A search that finds nothing, or a
  scheduled watchlist run where nothing changed, still gets a row explaining what happened — and
  costs nothing.
- **Paste a keyword or your own saved search URL.** Type plain keywords (including Korean, e.g.
  "나이키"), or paste a bunjang.co.kr search URL you've already run in your browser.

### What you get

One row per listing by default (turn off "Expand rows" in Advanced to get one row per search
instead, with the listings nested under `listings`).

| Field | Type | Description |
|---|---|---|
| `query` | text | The search you submitted, echoed back |
| `found` | boolean | `true` if Bunjang returned a real search response for this search |
| `status` | text | `OK` on a match; `NOT_FOUND`, `BLOCKED`, or `BAD_FORMAT` on a miss |
| `message` | text | Plain-English reason for a miss — only present when `found` is `false` |
| `searchQuery` | text | The keyword actually searched (parsed out of a pasted URL, if you gave one) |
| `listingCount` | number | Listings returned and billed for this search |
| `totalAvailable` | number | Total listings Bunjang reports matching this search, including ones not returned |
| `truncated` | boolean | `true` if more results existed than were returned |
| `newCount` | number | New listings this run (monitoring only) |
| `priceDropCount` | number | Price drops this run (monitoring only) |
| `listingId` | text | Bunjang's own listing ID (`pid`) |
| `title` | text | Listing title |
| `price` | number | Price in KRW, converted from Bunjang's own string-typed field |
| `currency` | text | Always `KRW` |
| `listingStatus` | text | `for_sale` on every listing this actor has observed live; any other value is reported as `status_<code>` rather than guessed |
| `conditionCode` | number | Bunjang's own raw condition code (1 or 2 observed live) — passed through as-is, since neither code reliably means "new" vs "used" in the titles sampled |
| `city` | text | Seller's neighbourhood, when Bunjang's listing carries one |
| `sellerType` | text | `business` when Bunjang's own `bizseller` or `proshop` flag is set, otherwise `private` |
| `favouriteCount` | number | How many users have favourited the listing |
| `freeShipping` | boolean | Bunjang's own free-shipping flag |
| `isPromoted` | boolean | `true` for a paid/ad listing |
| `category` | text | Bunjang's own category ID |
| `postedAt` | date | Listing's last-updated time, converted from Bunjang's unix timestamp |
| `imageUrl` | text (link) | Listing thumbnail image |
| `sellerHash` | text | Anonymous, stable hash of the seller's user ID |
| `sellerId` | text | **Only with "Include raw seller ID" on.** Bunjang's raw user ID |
| `changeType` | text | `new`, `price-drop`, or `seen` (monitoring only) |
| `isNew` | boolean | `true` on this listing's first appearance (monitoring only) |
| `previousPrice` | number | The price last recorded for this listing, when it dropped (monitoring only) |
| `priceDropPct` | number | Percentage drop from the previous recorded price (monitoring only) |
| `firstSeenAt` | date | When this watchlist first saw this listing (monitoring only) |
| `url` | text (link) | Permanent listing link (`m.bunjang.co.kr/products/<id>`) |
| `scrapedAt` | date | When this row was fetched |

Deselect any field in the Input tab's column picker to drop it from every row — `query`, `found`,
`status`, `message`, and `scrapedAt` always stay.

### Pricing

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed
per item only when data is actually found and returned — see
`.actor/pay_per_event.json` for exact prices. A miss is never charged.

### Monitoring / only new results

Turn on **"Only return results that are new or dropped in price since the last run"** and a search
line becomes a watchlist instead of a one-off dump:

- A listing counts as **new** the first time its Bunjang listing ID (`pid`) is returned by this
  watchlist.
- A listing counts as a **price drop** when its price falls by at least "Minimum price drop to
  alert on" (5% by default) since it was last seen — measured against the most recently seen price.
  Bunjang has no bidding system, so every listing's price is a real, comparable fixed price.
- Already-seen, unchanged listings are dropped before you're billed. A quiet run — nothing new,
  nothing cheaper — still finishes and returns one free row.
- The **first run has nothing to compare against.** By default it returns everything it finds as
  "new". Turn on **"Skip alerts on the first run"** to instead have the first run bank everything
  quietly with zero rows and zero charge, and start alerting from the second run on — this stops a
  fresh watchlist from firing a wall of "new listing" messages on day one.

**Schedule recipe.** Save this actor as an Apify **Task** with `deltaMode: true` and a `deltaName`
you choose, add an hourly (or daily) **Schedule**, and point the task's **webhook** at Discord,
Slack, Google Sheets, or an n8n/Make webhook URL to get pinged only when something actually changes.

**Coverage limitation.** This actor pages up to 1,000 listings per search (10 requests of 100), so a
narrow or moderately popular keyword is fully covered every run; an extremely high-volume keyword
can still exceed that in-between runs. Bunjang's own newest-first sort (`order=date`) means the
freshest listings are always fetched first, so monitoring stays reliable even when `truncated` is
`true`.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `searches` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~bunjang-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"searches":["iphone"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

4) Turn on "Only return results that are new or dropped in price since the last run" under
   Monitoring once you want a watchlist instead of a one-off dump — see "Monitoring / only new
   results" above.

### Input

```json
{
  "searches": [
    "iphone"
  ]
}
```

One search per line — keywords like "iphone" or "나이키", or paste a bunjang.co.kr search URL. Accepted formats: iphone, 나이키, https://api.bunjang.co.kr/api/1/find\_v2.json?q=iphone.

### Sample output

| query | found | status | searchQuery | listingCount | totalAvailable | truncated | newCount | priceDropCount | listings | listingId | url | title | price | currency | listingStatus | conditionCode | city | sellerType | favouriteCount | freeShipping | isPromoted | category | postedAt | imageUrl | sellerHash | sellerId | isNew | changeType | previousPrice | priceDropPct | firstSeenAt | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| iphone | true | OK | <search> | <listings returned> | <total matching on bunjang> | <more results were available> | <new listings this run> | <price drops this run> | \<all listings found (full list)> | \<bunjang listing id (pid)> | <listing link> | <title> | \<price (krw)> | <currency> | <listing status> | \<condition (raw bunjang code)> | <location> | <seller type> | <favourite count> | <free shipping> | <promoted listing> | <category id> | \<last updated (date)> | <image> | \<seller (anonymous hash)> | \<seller id (only with seller info on)> | \<is this listing new?> | <change type> | \<previous price (krw)> | \<price drop %> | <first seen on a run> | 1970-01-01T00:00:00.000Z |

A search that finds nothing comes back as a row with `"found": false` and is never charged.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~bunjang-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"searches":["iphone"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~bunjang-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"searches":["iphone"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~bunjang-listing-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"searches":["{{search}}"]}`, mapping the row's search into the `searches` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Bunjang Scraper | Apify" — the agent will find and run this actor.

### Tips

- Start monitoring with "Skip alerts on the first run" on for any watchlist you're setting up on a
  schedule — it avoids a wall of "new" alerts for your entire current search result on day one.
- `conditionCode` is Bunjang's own raw code, not decoded into "new"/"used" — the titles under both
  observed codes mix genuinely new and ordinary used items, so this actor doesn't invent a label the
  data can't support. Filter on keywords in the title (e.g. "새상품", "미개봉") if you need that.
- A `BLOCKED` status means Bunjang returned a 403, 429, or 503 — lowering "Max concurrency" or
  trying again shortly usually clears it; this actor doesn't need a proxy by default.
- Use all three Korean marketplace actors together (this one, `joonggonara-listing-lookup`,
  `daangn-listing-lookup`) for one alert feed across Korea's whole DIY-alert-bot territory — their
  shared column names make merging the three outputs straightforward in Sheets or n8n.

### vs. piotrv1001's scraper

The current Apify Store leader for Bunjang, `piotrv1001`'s actor, has 22 lifetime users and no
monitoring mode. This actor adds new-listing and price-drop monitoring as a first-class mode, and
bills only for listings actually delivered.

| | What it costs | What you get | Trade-off |
|---|---|---|---|
| **This actor** | $2 per 1,000 listings; nothing for a miss or a quiet monitoring run | Monitoring mode (new + price drop), anonymous seller hash, permanent listing link, up to 1,000 listings per search | Condition is a raw code, not a decoded "new"/"used" label |
| piotrv1001's scraper | Unknown / no monitoring | A one-off dump | No monitoring |
| Doing it yourself | Your time to build and maintain a scraper, a seen-listing store, and a price-tracking layer | The same data | This actor's pagination and monitoring state are the maintenance burden it absorbs |

### Data & privacy

This actor reads public search results that anyone can see without logging in. It doesn't log in,
solve CAPTCHAs, or reveal hidden contact details. Seller identity is off by default: you get a
private/business flag (`sellerType`) and an anonymous seller hash so you can group listings by
seller without names — Bunjang's own search results carry no seller display name to expose in the
first place. Turning on "Include raw seller ID" makes you responsible for having a lawful reason to
process that personal data. Not affiliated with Bunjang / 번개장터.

**Is this allowed?** It collects the same public listing data your browser shows, for the searches
you choose. It's built for monitoring a search, not for copying the marketplace. South Korea's
Supreme Court held in 2022 (case 2021Do1533) that scraping publicly available web data did not
breach copyright or information-protection law — favourable context, not a substitute for checking
that your own use fits Bunjang's terms and your local law.

### FAQ

**Why is a row empty, or why does `found` say `false`?**
Either the input line was blank (`status: BAD_FORMAT`), Bunjang returned a 403/429/503
(`status: BLOCKED`), or the search matched nothing right now (`status: NOT_FOUND`). Check the
`message` column for the specific reason. None of these are billed.

**Am I charged for a quiet monitoring run?**
No. When monitoring finds nothing new and no price drops, you get one row with `listingCount: 0` —
`Actor.charge()` only fires when `listingCount` is greater than zero.

**Why is `price` a number when Bunjang's own API returns it as text?**
Bunjang's search API sends `price`, the listing ID, and a couple of other fields as JSON strings
(confirmed live), not numbers — this actor converts them so a downstream price filter or a Sheets
formula gets a real number, not text that only looks like one.

**What does `listingStatus: for_sale` mean, and are there other values?**
Every listing sampled live across three different searches came back on-sale — this actor doesn't
know of a documented way to ask Bunjang's own search API for sold items too. If that ever changes
you may see a `status_<code>` value this actor hasn't mapped a label for yet — it's passed through
rather than hidden.

**Do I need to configure proxies?**
No. This actor uses Apify's default proxy configuration (no proxy group) out of the box — Bunjang
doesn't block plain requests from Apify's datacenter IPs.

**Can an AI agent call this directly?**
Yes. It's registered on the Apify MCP server — an agent in Claude, Cursor, or another MCP client
can find and run it by name ("Bunjang Scraper | Apify"), or you can call the REST endpoint shown
above from any script or workflow tool.

### Related actors

- [Joonggonara Scraper](https://apify.com/accountable_eel/joonggonara-listing-lookup) — the same
  search and monitoring shape for Joonggonara, Korea's other major second-hand marketplace.
- [Daangn Scraper](https://apify.com/accountable_eel/daangn-listing-lookup) — the same shape for
  Daangn (Karrot Market), Korea's neighbourhood-scoped classifieds app.

# Actor input Schema

## `searches` (type: `array`):

One search per line — keywords like "iphone" or "나이키", or paste a bunjang.co.kr search URL. Accepted formats: iphone, 나이키, https://api.bunjang.co.kr/api/1/find\_v2.json?q=iphone. You're only charged for the ones we actually find — a miss costs nothing.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

## `maxResults` (type: `integer`):

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `maxListingsPerSearch` (type: `integer`):

Bunjang returns up to 100 listings per request; this actor pages automatically above that, up to 1000 per search. You pay per listing returned, so this is also your budget control.

## `minPrice` (type: `integer`):

Optional. Drop listings priced below this. Leave empty for no minimum. Applied after fetching (no confirmed API price-range parameter).

## `maxPrice` (type: `integer`):

Optional. Drop listings priced above this. Leave empty for no maximum. Applied after fetching (no confirmed API price-range parameter).

## `deltaMode` (type: `boolean`):

Turns this actor into a monitor. A listing counts as new when Bunjang's own listing ID (pid) hasn't been returned by a previous run of the same watchlist; a price drop counts when a previously-seen listing's price has fallen (see "Minimum price drop" below). Already-reported listings are dropped before you're billed, so a run with nothing new or dropped costs only the run fee. The first run has nothing to compare against, so it returns and remembers everything; from the second run on you get only what changed.

## `deltaName` (type: `string`):

Leave empty and we derive one from this run's filters, so two schedules with different filters keep separate memories. Type your own name to keep one memory across a filter change, or to have two schedules share one.

## `alertOnNew` (type: `boolean`):

Part of "Alert on" (split into two checkboxes so the Console can render it as a plain toggle pair). On by default.

## `alertOnPriceDrop` (type: `boolean`):

Part of "Alert on". On by default.

## `minPriceDropPct` (type: `integer`):

Bunjang has no bidding system, so every listing's price is a real, comparable fixed price. Default 5%.

## `skipFirstRun` (type: `boolean`):

On: the run that first starts a watchlist banks every listing silently — no rows, no charge — instead of reporting everything that already existed as "new". Off (default): the first run returns everything it finds, all marked new.

## `includeSellerInfo` (type: `boolean`):

Off by default. On: adds the seller's raw Bunjang user ID to every row, in addition to the always-on anonymous seller hash. Bunjang's search results carry no seller display name to expose. Turning this on makes you responsible for having a lawful reason to process that personal data.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each listing found gets its own row instead of being grouped under its search. You're still only charged once per search, no matter how many rows it produces.

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

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

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

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "searches": [
    "iphone"
  ],
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "maxListingsPerSearch": 100,
  "deltaMode": false,
  "deltaName": "",
  "alertOnNew": true,
  "alertOnPriceDrop": true,
  "minPriceDropPct": 5,
  "skipFirstRun": false,
  "includeSellerInfo": false,
  "columns": [
    "searchQuery",
    "listingCount",
    "totalAvailable",
    "truncated",
    "newCount",
    "priceDropCount",
    "listings",
    "listingId",
    "url",
    "title",
    "price",
    "currency",
    "listingStatus",
    "conditionCode",
    "city",
    "sellerType",
    "favouriteCount",
    "freeShipping",
    "isPromoted",
    "category",
    "postedAt",
    "imageUrl",
    "sellerHash",
    "sellerId",
    "isNew",
    "changeType",
    "previousPrice",
    "priceDropPct",
    "firstSeenAt"
  ],
  "expandRows": true,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

No description

# 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 = {
    "searches": [
        "iphone"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/bunjang-listing-lookup").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 = {
    "searches": ["iphone"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/bunjang-listing-lookup").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 '{
  "searches": [
    "iphone"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/bunjang-listing-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/bunjang-listing-lookup"
        }
    }
}
```

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/kSRzpcbnpuyMt5e9k/builds/vJ7OPWqV61WjK8u7A/openapi.json