thelayoff.com APIwww.thelayoff.com ↗
Access TheLayoff.com forum posts by company slug, with titles, dates, authors, reactions, view counts, and full reply threads via 2 REST endpoints.
curl -X GET 'https://api.parse.bot/scraper/7ebc6abd-1ea4-4195-af2a-531a49ef94ff/get_posts?page=1&sort=new&company=google' \ -H 'X-API-Key: $PARSE_API_KEY'
Get a paginated list of forum posts for a specific company's layoff discussion page. Returns post titles, content previews, dates, authors, view counts, reactions, and reply counts.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (1-based). |
| sort | string | Sort order: 'new' for newest first, 'active' for most recently active. |
| company | string | Company slug used in the URL path (e.g., 'apple', 'google', 'amazon', 'meta'). |
{
"type": "object",
"fields": {
"page": "integer, the current page number",
"sort": "string, the sort order applied",
"posts": "array of post objects with title, url, post_id, content, date, date_display, author, views, reactions_total, reactions_up, reactions_down, replies, last_reply_date",
"company": "string, the company slug used in the request",
"posts_count": "integer, number of posts returned on this page",
"company_title": "string, descriptive title of the company's discussion page",
"has_next_page": "boolean, whether a next page of results exists",
"has_previous_page": "boolean, whether a previous page exists"
},
"sample": {
"data": {
"page": 1,
"sort": "new",
"posts": [
{
"url": "https://www.thelayoff.com/t/1kq7pfwbw",
"date": "2026-04-27T14:46:29Z",
"title": "Why does iOS 26 S_U_C_K ?",
"views": 0,
"author": "Anonymous",
"content": "It's a perfect example of what's wrong with Apple...",
"post_id": "@OP+1kq7pfwbw",
"replies": 1,
"date_display": "16 days ago",
"reactions_up": 0,
"reactions_down": 0,
"last_reply_date": "2026-04-27T17:23:20Z",
"reactions_total": 0
}
],
"company": "apple",
"posts_count": 40,
"company_title": "Topics regarding layoffs at Apple Inc.",
"has_next_page": true,
"has_previous_page": false
},
"status": "success"
}
}About the thelayoff.com API
The TheLayoff.com API provides 2 endpoints for retrieving company-specific layoff forum data, including post listings via get_posts and full thread details via get_post_detail. Each post object exposes title, author, content, ISO 8601 date, view count, upvote and downvote reaction counts, and reply count. The get_posts endpoint supports pagination and sort order, while get_post_detail returns complete reply threads with per-reply reactions and author attribution.
What the API Returns
The get_posts endpoint returns a paginated list of forum posts for any company supported by TheLayoff.com, identified by a company slug such as apple, google, or amazon. Each response includes the current page number, sort order, a has_next_page and has_previous_page flag for cursor navigation, the company_title string, and a posts array. Every post object in that array carries a post_id, title, url, truncated content preview, date (ISO 8601), date_display (relative human-readable string), author, views, reactions_total, reactions_up, and reactions_down.
Thread Detail and Replies
The get_post_detail endpoint accepts a post_id obtained from get_posts and returns the full original post alongside its complete reply thread. The top-level response includes the post's title, content, author, date, date_display, views, reactions_up, reactions_total, and url. The replies array contains individual reply objects, each with reply_id, content, author, date, date_display, reactions_total, reactions_up, and reactions_down. The endpoint automatically strips the @OP+ prefix if it appears in a supplied post_id.
Filtering and Pagination
The get_posts endpoint accepts three optional parameters: company (the URL slug for the company), page (1-based integer for pagination), and sort (new for newest-first or active for most recently active threads). There is no full-text search parameter; filtering by keyword or date range within results must be handled client-side. Posts from multiple companies require separate requests, one per company slug.
- Track layoff discussion activity at a specific company by monitoring
posts_countandreactions_totalover time usingget_posts. - Aggregate community sentiment signals by comparing
reactions_upandreactions_downacross posts and replies for a given company. - Build a layoff news feed by polling
get_postswithsort=newacross multiple company slugs and surfacing the latestdatevalues. - Analyze reply volume per post using
get_post_detailto measure community engagement depth beyond surface-level view counts. - Extract author participation patterns across threads by collecting
authorfields from both posts and reply objects. - Archive full thread content including all
repliesfor HR research, journalism, or workforce trend analysis. - Compare discussion velocity across companies by tracking
has_next_pagedepth andviewsgrowth for different company slugs.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does TheLayoff.com offer an official developer API?+
What does `get_posts` return versus `get_post_detail`, and when should I use each?+
get_posts returns a paginated list of post summaries for a company slug — titles, truncated content previews, reaction counts, view counts, and reply counts. It is suited for discovery and feed construction. get_post_detail returns the full original post content plus the complete replies array with per-reply attribution, and should be used when you need the full thread text and all reactions at the reply level.Can I search for posts by keyword or filter by date range?+
get_posts endpoint supports sorting by new or active and pagination via the page parameter, but does not currently expose keyword search or date-range filtering as query parameters. Results can be filtered client-side using the date (ISO 8601) and content fields returned in each post object. You can fork this API on Parse and revise it to add a keyword or date-filter endpoint.Does the API cover all companies listed on TheLayoff.com, or only a subset?+
get_posts endpoint accepts any company slug that corresponds to a valid company discussion page on TheLayoff.com — such as apple, amazon, or meta. Coverage is limited to companies with active forum pages on the site. There is no endpoint that lists all available company slugs. You can fork this API on Parse and revise it to add a company-discovery or slug-listing endpoint.Is any user-identifying information exposed in post or reply objects?+
author field as a display name string for both posts and replies, matching what is publicly visible on TheLayoff.com forum pages. No email addresses, user IDs, profile links, or private account data are included in any response object.