# Bluesky Scraper: Posts, Profiles & Followers (`sz022/bluesky-scraper`) Actor

Scrape Bluesky without a login: profile posts, search results, full threads with replies, quotes, likers and reposters, profiles and followers. Image alt text, video links, verification, reply settings and hidden replies included. Export to CSV, Excel or JSON, or use the API.

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

## Pricing

from $1.50 / 1,000 post scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

### What is Bluesky Scraper?

Bluesky's own app shows you one profile, one thread or one search at a time, and copies nothing out. This Actor reads the same public data in bulk and hands it back as a table you can filter, export or feed into your own tools.

Give it any mix of:

- **Profiles** (handles, DIDs or profile URLs): one profile row each with exact follower, follow and post counts, then the profile's recent **posts**, and optionally its **followers** and **follows**.
- **Post URLs**: the post itself, plus as much of its **reply thread**, its **quote posts**, and the accounts that **liked** and **reposted** it as you ask for.
- **Search queries**: posts matching a word, phrase, hashtag or Bluesky search operator, newest first or by Bluesky's Top ranking, with date and language filters.

No Bluesky account or app password is needed. Everything comes from Bluesky's public API, the same one the logged-out web app uses.

Because it runs on Apify, you can **schedule** it (track a hashtag every hour, a list of accounts every morning), call it through the **API**, connect it to Make, Zapier or Google Sheets, and export as **CSV, Excel or JSON**.

### What you get that most Bluesky scrapers leave out

- **Image alt text** and dimensions for every image, and the **video playlist (HLS) and thumbnail** for every video, with its alt text and file size.
- **Verification details**: not just whether an account is verified, but **who verified it** (Bluesky, or a trusted verifier such as a newsroom) and when.
- **Reply settings and hidden replies**: who is allowed to reply to a post (everyone, nobody, followers, people mentioned, a list), and which replies its author hid. Thread replies come with `isHiddenReply`.
- **Thread position**: `opThreadPostIndex` / `opThreadPostCount` when a post is part of its author's numbered thread (1/5, 2/5...).
- **Bridged posts**: for accounts bridged in from Mastodon and the fediverse through Bridgy Fed, the **original post URL and text**, and which network the account comes from.
- **Handle history** (optional): every handle an account has used and since when, from the public PLC directory, plus the server that hosts it.
- **Links, mentions and hashtags** exactly as the author's app marked them, and the full link-card (title, description, thumbnail) of any shared link.
- **Labels**: the author's own content warnings, and labels set by moderation services, kept apart.
- **Emails and links found in bios**, for profiles and for every listed follower.
- **Bookmark counts** next to likes, reposts, replies and quotes.

### How to scrape Bluesky

1. Open the **Input** tab. Fill in any of **Profiles**, **Post URLs** and **Search queries**; you can use all three in one run.
2. Set how much you want for each: posts per profile, replies, quotes, likers and reposters per post, posts per search. Anything left at 0 is skipped and costs nothing.
3. Click **Start**. A profile with 100 posts takes about a second; a thread with a few hundred replies a few seconds.
4. Open the **Output** tab, or export the dataset. Every row has a `type` (`post`, `profile`, `user` or `status`), so a spreadsheet filter separates them.

### Input example

```json
{
  "profiles": ["bsky.app", "@jay.bsky.team"],
  "maxPostsPerProfile": 50,
  "includeReposts": false,
  "maxFollowersPerProfile": 200,
  "postUrls": ["https://bsky.app/profile/bsky.app/post/3l6oveex3ii2l"],
  "maxRepliesPerPost": 100,
  "maxLikersPerPost": 100,
  "searchQueries": ["#buildinpublic", "\"open social\" lang:en"],
  "maxPostsPerSearch": 500,
  "searchSince": "7 days"
}
```

### Output

One dataset, four row types. Fields that do not apply to a row are absent or `null`. **Unknown is `null`, never a made-up `0`.** Times are ISO-8601 as Bluesky sends them; counts are numbers.

#### Post rows (`type: "post"`)

| Field | Notes |
|---|---|
| `url`, `uri`, `cid`, `postId` | Web link, AT URI, content hash, record key |
| `author` | `did`, `handle`, `displayName`, `avatar`, `profileUrl`, `createdAt`, `verification` (`verifiedStatus`, `trustedVerifierStatus`, `verifiedBy` with issuer handle and date), `selfLabels`, `moderationLabels`, `bridgedFrom`, `pronouns` |
| `text`, `langs`, `createdAt`, `indexedAt` | |
| `likeCount`, `repostCount`, `replyCount`, `quoteCount`, `bookmarkCount` | |
| `links`, `mentions`, `hashtags`, `tags` | From the post's rich-text facets; `mentions` has DID and handle |
| `embedType` | `images`, `video`, `external` (link card), `quote`, `quoteWithMedia`, `record` (a quoted feed, list or starter pack), or `null` |
| `images` | `url`, `thumbnail`, `alt`, `width`, `height`, `mimeType`, `sizeBytes` |
| `video` | `playlistUrl` (HLS .m3u8), `thumbnail`, `alt`, `width`, `height`, `mimeType`, `sizeBytes`, `captionLanguages` |
| `externalLink` | `url`, `title`, `description`, `thumbnail` |
| `quotedPost` | The quoted post with its own author, text, counts, media and alt text; `status` is `not_found`, `blocked` or `detached` when it cannot be shown |
| `quotedRecord` | A quoted feed, list, starter pack or labeler |
| `selfLabels`, `moderationLabels` | Content warnings set by the author, and labels from moderation services (with labeler and date) |
| `isReply`, `replyParentUri`/`Url`/`AuthorHandle`, `replyRootUri`/`Url`/`AuthorHandle` | |
| `threadgate` | `whoCanReply`, `allowedRepliers`, `allowedLists`, `hiddenReplies`, `hiddenRepliesCount` |
| `isHiddenReply`, `threadDepth` | Thread replies only |
| `opThreadPostIndex`, `opThreadPostCount` | Position in the author's own numbered thread, when Bluesky reports it |
| `isBridged`, `bridgyOriginalUrl`, `bridgyOriginalText` | Bridged fediverse posts |
| `isRepost`, `repostedBy`, `repostedAt`, `repostUri`, `isPinned` | Profile feeds |
| `source`, `position` | `authorFeed`, `search`, `post`, `reply` or `quote`, and the rank within it |
| `profileHandle`, `searchQuery`, `searchHitsTotal`, `targetPostUrl` | What the row was found through |
| `recordExtras` | Any other fields the author's app stored on the post |

#### Profile rows (`type: "profile"`)

`did`, `handle`, `handleIsValid`, `displayName`, `profileUrl`, `description`, `descriptionLinks`, `descriptionEmails`, `descriptionMentions`, `descriptionHashtags`, `avatar`, `banner`, `followersCount`, `followsCount`, `postsCount`, `createdAt`, `indexedAt`, `verification`, `selfLabels`, `moderationLabels`, `loggedOutVisibilityDisabled`, `pinnedPostUri`, `pinnedPostUrl`, `listsCount`, `feedsCount`, `starterPacksCount`, `isLabeler`, `chatAllowIncoming`, `activitySubscriptionsAllowed`, `joinedViaStarterPack`, `liveStatus`, `pronouns`, `website`, `bridgedFrom`, and with **Handle history** on, `handleHistory` (`[{handle, since}]`) and `pdsEndpoint`.

#### User rows (`type: "user"`)

Followers, follows, likers and reposters: `relation` (`follower`, `follow`, `liker`, `reposter`), `did`, `handle`, `displayName`, `profileUrl`, `description` with its links and emails, `avatar`, `createdAt`, `verification`, labels, `position`, `relatedToHandle` or `targetPostUrl`, and `likedAt` for likers. The list endpoints do not carry counts; turn on **Full profiles for listed accounts** to get each as a profile row with counts instead.

#### Status rows (`type: "status"`)

One for every input that returned nothing or stopped short, so 10 inputs in means 10 visible outcomes. `INPUT_SUMMARY` in the key-value store lists all of them, including the ones that worked.

| `status` | Meaning | Charged |
|---|---|---|
| `not_found` | No such profile or post (deleted, or the account is gone) | No |
| `hidden_by_user` | The account asked Bluesky not to be shown to logged-out visitors (see below) | No |
| `unavailable` | Account taken down, deactivated or suspended | No |
| `invalid_input` | Not a handle, DID, profile URL or post URL | No |
| `no_results` | The search matched nothing | No |
| `blocked` | Bluesky refused the logged-out request (see search below) | No |
| `rate_limited`, `error`, `parse_error` | Bluesky kept failing or answered with something unexpected | No |
| `parse_error` on a `post`, `profile` or `user` row | One item in a page Bluesky sent without what such a row needs (an author, a valid URI); the rest of the page is unaffected | No |
| `partial` | The input returned some rows, then the run stopped (max charge reached, timeout) | Only the rows delivered |
| `not_processed` | The run stopped before reaching this input | No |

### Output example

A post row from a real run on 2026-10-18, trimmed:

```json
{
  "type": "post",
  "url": "https://bsky.app/profile/bsky.app/post/3mxyyerrxak2m",
  "author": {
    "handle": "bsky.app",
    "displayName": "Bluesky",
    "verification": { "verifiedStatus": "none", "trustedVerifierStatus": "valid", "verifiedBy": [] }
  },
  "text": "v1.135 is live!\n\nYou can now browse quote posts by Top in addition to Latest. ...",
  "createdAt": "2026-10-16T16:23:26.498Z",
  "likeCount": 1230,
  "repostCount": 194,
  "replyCount": 171,
  "quoteCount": 77,
  "bookmarkCount": 77,
  "embedType": "video",
  "video": {
    "playlistUrl": "https://video.bsky.app/watch/did%3Aplc%3Az72i7hdynmk6r22z27h6tvur/bafkreiat76ppqns6bcnxnt6etzlyoar4o75v6wrzwjbh342oxbsebyun5e/playlist.m3u8",
    "thumbnail": "https://video.bsky.app/watch/did%3Aplc%3Az72i7hdynmk6r22z27h6tvur/bafkreiat76ppqns6bcnxnt6etzlyoar4o75v6wrzwjbh342oxbsebyun5e/thumbnail.jpg",
    "alt": "A video showing the Bluesky interface as a user clicks through to see quotes on an individual posts. ...",
    "width": 1000,
    "height": 1000,
    "sizeBytes": 3850070
  },
  "threadgate": { "whoCanReply": "everyone", "hiddenRepliesCount": 2 }
}
```

### How much does it cost to scrape Bluesky?

You pay per row returned, nothing per minute, and nothing for inputs that fail.

| Event | What it is | Price | Per 1,000 |
|---|---|---|---|
| `post-scraped` | One post row: from a profile, a search, a post URL, a thread reply or a quote | $0.0015 | $1.50 |
| `profile-scraped` | One profile row with counts (input profiles, and listed accounts when **Full profiles** is on) | $0.0015 | $1.50 |
| `user-listed` | One follower, follow, liker or reposter | $0.0005 | $0.50 |
| `handle-history` | Handle history added to one profile row (only with **Handle history** on) | $0.001 | $1.00 |

Status rows are free. A profile with 100 posts costs $0.1515; the same profile with 1,000 followers listed adds $0.50. Apify's free plan ($5 a month) covers about 3,300 posts or 10,000 followers.

#### How do I cap what a run can spend?

Set a maximum charge for the run. Rows are written and charged together, one API page at a time, through Apify's own charging call: it writes only as many rows as the remaining budget covers and charges exactly those, so you are never charged for a row that is not in your dataset. When the budget runs out, the run stops, the input in progress is marked `partial`, and every input it did not reach gets a free `not_processed` row. Handle history is charged only for profile rows that were delivered with it; a row the budget cannot pay both for goes out without it. If Apify cannot record a charge, the run stops and does no further work; a failed charge is never sent a second time, so nothing is charged twice. The run's timeout is watched inside every page and retry too: close to it, the run stops reading and still writes the status rows.

### Limits and honest caveats

- **Search uses an undocumented endpoint.** Bluesky's documented public API refuses post search without a login (403). The host Bluesky's own app uses, `api.bsky.app`, currently answers the first page of a search logged out but refuses its next-page cursor. So "Latest" searches page backwards by date instead, which works for any number of posts; **"Top" stops at 100 posts**, and so does a query made of **several hashtags alone** (`#art #ai`): search them one per line instead. If Bluesky closes logged-out search, search inputs come back `blocked` and free, and profiles and post URLs keep working.
- **Threads** come in Bluesky's own reply order, up to the depth you set. Very large threads are returned as far as Bluesky's API returns them in one answer.
- **Likers, reposters, followers and follows** are paged until the number you asked for or the end of the list, newest first.
- **Logged-out data only.** Nothing that needs an account: no "followed by people you know", no muted words, no feeds you subscribe to.
- **Accounts that asked not to be shown to logged-out visitors are left out by default.** Bluesky lets people set this (a `!no-unauthenticated` label); its web app then hides them from anyone signed out, although the API still returns them. This Actor follows the same choice: a profile or post URL of such an account comes back as a free `hidden_by_user` row, and their posts, replies, quotes and list entries are skipped (a quoted post of theirs shows only `status: "hidden_by_user"` and its link). Turn on **Include accounts hidden from logged-out visitors** to read them anyway; their rows then carry `loggedOutVisibilityDisabled: true`.
- No proxy is needed or used by default. If a very large run meets Bluesky's per-IP rate limits, the Actor waits as long as Bluesky asks and retries; turning on Apify's datacenter proxy makes each retry come from a fresh IP.

#### What happens if Apify restarts a run?

Apify sometimes moves a running Actor to another server, which restarts it. The Actor saves its place when each input starts and ends, and whenever Apify signals a migration. After a restart it reads back the rows the interrupted input already put in the dataset and skips them, so they are not published or charged a second time, then carries on. Relative dates such as `7 days` keep the value they had when the run first started.

### FAQ

#### Is scraping Bluesky allowed?

This Actor reads only what Bluesky publishes to anyone without an account, through Bluesky's public API, at a modest rate. Bluesky's data is public by design: every post and profile lives in an open network. Accounts that asked not to be shown to logged-out visitors are left out unless you opt in. You are still responsible for how you use what you collect, including personal data rules such as GDPR.

#### Do I need a Bluesky account or app password?

No.

#### Can I monitor a hashtag or keyword over time?

Yes. Save the input as a task with a search query, set **Posted after** to a relative value such as `1 day`, and schedule it daily. Each run returns the posts of the last day.

# Actor input Schema

## `profiles` (type: `array`):

Bluesky handles, DIDs or profile URLs, one per line: bsky.app, @jay.bsky.team, did:plc:z72i7hdynmk6r22z27h6tvur or https://bsky.app/profile/bsky.app. A name without a dot is read as name.bsky.social. Each profile gives one profile row, then its posts, followers and follows as set below.

## `maxPostsPerProfile` (type: `integer`):

How many of each profile's most recent posts to return. 0 returns the profile row only.

## `feedFilter` (type: `string`):

The same choice as the tabs on a Bluesky profile.

## `includeReposts` (type: `boolean`):

Posts the profile reposted, marked with isRepost, repostedBy and repostedAt. Off returns only the profile's own posts.

## `includePinnedPost` (type: `boolean`):

Puts the profile's pinned post first, marked isPinned, whatever its date.

## `postsNewerThan` (type: `string`):

Optional. Stop reading a profile's posts at this date: 2026-10-01, or a relative value such as 7 days.

## `maxFollowersPerProfile` (type: `integer`):

How many of each profile's followers to list, newest first. 0 lists none.

## `maxFollowsPerProfile` (type: `integer`):

How many of the accounts each profile follows to list. 0 lists none.

## `enrichUsers` (type: `boolean`):

Followers, follows, likers and reposters come as user rows: handle, name, bio, avatar, verification. Turn this on to get each as a full profile row with follower, follow and post counts instead. Charged as a profile row rather than a user row.

## `includeHandleHistory` (type: `boolean`):

Every handle each profile has used and since when, plus the server hosting it, from the public PLC directory. One extra request per profile, charged as its own event.

## `postUrls` (type: `array`):

Bluesky post URLs or at:// URIs, one per line, for example https://bsky.app/profile/bsky.app/post/3l6oveex3ii2l. Each gives the post itself, and the replies, quotes, likers and reposters asked for below.

## `maxRepliesPerPost` (type: `integer`):

How many replies to return from each post's thread, in Bluesky's own order, nested replies included. Each row has its threadDepth and whether the author hid it. 0 returns none.

## `threadDepth` (type: `integer`):

How many levels of replies to follow: 1 is direct replies only.

## `maxQuotesPerPost` (type: `integer`):

How many posts quoting each post to return. 0 returns none.

## `maxLikersPerPost` (type: `integer`):

How many accounts that liked each post to list, newest first, with likedAt. 0 lists none.

## `maxRepostersPerPost` (type: `integer`):

How many accounts that reposted each post to list. 0 lists none.

## `searchQueries` (type: `array`):

Words, phrases or hashtags to search posts for, one per line. Bluesky's search syntax works: "exact phrase", from:bsky.app, mentions:bsky.app, domain:example.com, #hashtag, lang:en.

## `maxPostsPerSearch` (type: `integer`):

How many posts to return for each query. Sorted by Top, a search returns at most 100.

## `searchSort` (type: `string`):

Latest is newest first and has no limit; Top is Bluesky's ranking and stops at 100 posts.

## `searchSince` (type: `string`):

Optional: 2026-10-01, or a relative value such as 7 days.

## `searchUntil` (type: `string`):

Optional: 2026-10-15, or a relative value such as 1 day.

## `searchLanguage` (type: `string`):

Optional two-letter language code, such as en, ja or pt, matched against the language the author set on the post.

## `includeHiddenAccounts` (type: `boolean`):

Some people ask Bluesky not to show their account to visitors who are not signed in. Their profiles, posts and list entries are left out by default: a profile or post URL of theirs comes back as hidden_by_user (free), and their posts in feeds, threads and searches are skipped. Turn this on only if you have a reason to read them anyway.

## `abortAfterConsecutiveFailures` (type: `integer`):

Ends the run early when Bluesky stops answering. Profiles and posts that do not exist do not count toward this. 0 never stops early.

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

Bluesky's public API needs no proxy, so none is used by default. Turn on Apify's datacenter proxy if a run keeps hitting rate limits: each retry then goes out from a fresh IP. Residential and SERP groups are not used; a run that asks for them falls back to datacenter.

## Actor input object example

```json
{
  "profiles": [
    "bsky.app"
  ],
  "maxPostsPerProfile": 10,
  "feedFilter": "posts_with_replies",
  "includeReposts": true,
  "includePinnedPost": false,
  "maxFollowersPerProfile": 0,
  "maxFollowsPerProfile": 0,
  "enrichUsers": false,
  "includeHandleHistory": false,
  "postUrls": [
    "https://bsky.app/profile/bsky.app/post/3l6oveex3ii2l"
  ],
  "maxRepliesPerPost": 5,
  "threadDepth": 10,
  "maxQuotesPerPost": 0,
  "maxLikersPerPost": 0,
  "maxRepostersPerPost": 0,
  "searchQueries": [
    "apify"
  ],
  "maxPostsPerSearch": 10,
  "searchSort": "latest",
  "includeHiddenAccounts": false,
  "abortAfterConsecutiveFailures": 5,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

One row per post, profile, follower, follow, liker or reposter, plus a status row for each input that failed or stopped short. Unknown values are null, never 0.

## `inputSummary` (type: `string`):

Every input with its status, the number of rows it returned and the reason when it returned none.

# 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 = {
    "profiles": [
        "bsky.app"
    ],
    "maxPostsPerProfile": 10,
    "postUrls": [
        "https://bsky.app/profile/bsky.app/post/3l6oveex3ii2l"
    ],
    "maxRepliesPerPost": 5,
    "searchQueries": [
        "apify"
    ],
    "maxPostsPerSearch": 10,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("sz022/bluesky-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 = {
    "profiles": ["bsky.app"],
    "maxPostsPerProfile": 10,
    "postUrls": ["https://bsky.app/profile/bsky.app/post/3l6oveex3ii2l"],
    "maxRepliesPerPost": 5,
    "searchQueries": ["apify"],
    "maxPostsPerSearch": 10,
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("sz022/bluesky-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 '{
  "profiles": [
    "bsky.app"
  ],
  "maxPostsPerProfile": 10,
  "postUrls": [
    "https://bsky.app/profile/bsky.app/post/3l6oveex3ii2l"
  ],
  "maxRepliesPerPost": 5,
  "searchQueries": [
    "apify"
  ],
  "maxPostsPerSearch": 10,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call sz022/bluesky-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sz022/bluesky-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/pLCbv3aaL3KEYOsTo/builds/eUKNBJsrOWXC5thiR/openapi.json