TeamBlind Scraper

Scrape posts, comments, topic feeds, and company-specific feeds from TeamBlind — the anonymous workplace community used by tech employees at Google, Apple, Microsoft, Meta, Amazon, Netflix, and thousands of other companies.

TeamBlind is login-walled. You must paste a logged-in browser cookie. Without it, TeamBlind serves a logged-out shell that contains no post data.

What you can do with it

• Search posts by keyword — track mentions of layoffs, comp negotiations, RSU grants, specific companies, etc.
• Fetch a single post + comments — get full thread content (post body + every comment).
• Browse topic feeds — Career, Compensation, Interview, Tech, Layoffs, Startups, Investing, Real Estate, and more.
• Per-company feed — pull posts from a specific company's channel (Google, Apple, Stripe, Uber, etc.).
• Paste any teamblind.com URL — the scraper auto-detects topic / company / search / post.

Modes

Mode	What it does	Required input
searchPosts	TeamBlind search by keyword	query
byPost	Single post detail + comments	postUrls[]
byTopic	Browse a topic feed (Career / Compensation / Interview / ...)	topic
byCompany	Browse one or more company feeds	companies[]
byUrl	Auto-detect from any teamblind.com URL	postUrls[]

How to extract your TeamBlind cookie

1. Sign in at https://www.teamblind.com.
2. Open the browser DevTools (F12 on Chrome / Edge / Firefox).
3. Go to the Network tab. Reload the page.
4. Click any request to teamblind.com. In the right pane, look for the Request Headers section.
5. Find the line starting with Cookie:. Copy the entire value after Cookie: (everything on that line). It will look like: b_session_id=AbcDef...; b_user=...; some_other=...; ...
6. Paste this entire string into the TeamBlind cookie header input field in this actor. The actor sends it verbatim as the Cookie HTTP header.

The cookie typically stays valid for several weeks. If TeamBlind starts returning a logged-out shell again, re-export.

Output fields

Post record (recordType=post)

Field	Notes
id	Numeric post ID
alias	URL-safe alias (used in /post/{alias})
title	Post title
content	Post body text
memberNickname	Author's anonymized handle
boardName	Board / company / region label
boardId, channelId	Numeric IDs for filtering
createdAt	Relative time ("4d", "1h")
writedAt	ISO 8601 absolute timestamp
likeCount	Likes
commentCount	Comment count
viewCount	View count
isPoll, isHot, isHighlight	Booleans
tags[]	Tags (rare)
wasCompanies[]	Author's previous companies (when shown)
url	Direct post URL
sourceType	topic / company / search / post (where it was found)

Comment record (recordType=comment, only when mode=byPost and includeComments=true)

Field	Notes
id	Numeric comment ID
parentPostAlias	Alias of the parent post
content	Comment text
memberNickname	Author handle
createdAt / writedAt	Times
likeCount, replyCount	Counts
boardName	Board label
url	Parent post URL

Error record (recordType=error)

Emitted when a fetch fails or returns a logged-out shell. Includes url, reason, httpStatus (when known), and the requested context (sourceType, topic, query, etc.).

Defaults (daily-test prefill)

mode=searchPosts, query="layoffs", maxItems=10 — but the daily test will fail because no real cookieHeader is provided. This is expected for credential-gated actors per the Apify pattern: the actor emits a clear status message ("TeamBlind requires cookieHeader...") and exits cleanly with 0 records. Provide a real cookie to verify locally before scheduling production runs.

FAQs

Why does the daily test always fail? Because TeamBlind requires a logged-in cookie. The Apify daily test framework cannot supply your personal cookie; once you provide one in your run config, all modes work.

My cookie expired — how do I tell? The actor emits a recordType=error record with reason=login_wall and sets the run status message to "TeamBlind returned a logged-out shell — cookieHeader is missing or expired".

Are post IDs stable? Yes — id and alias are stable post identifiers. Use alias to construct deep links.

What about TeamBlind's Korean variant (kr.teamblind.com)? Set country=kr. The actor swaps the host domain accordingly.

Does it work without a proxy? Yes for most accounts. The actor auto-escalates to Apify residential proxy on 403 / 429 / 5xx blocks if autoEscalateOnBlock=true (default).

Will TeamBlind ban my account? Posts and feeds are read-only HTTP GETs at moderate rate (1 req every ~0.5s). We've seen no bans for read traffic, but use at your own risk — TeamBlind ToS prohibits automated scraping.

Limitations

• Cookie required. No way around it.
• TeamBlind only embeds ~5–25 posts per topic page in SSR; deeper pagination would require client-side API replays not yet exposed (planned for v2).
• Comment threads are flat in this version (no parent/child relationships rebuilt).
• Korean (kr.teamblind.com) feed structure is identical, but topic slugs are different.

Pricing

You are billed per Apify Compute Unit. There is no per-record fee on this actor.