> For the complete documentation index, see [llms.txt](https://docs.intellizence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intellizence.com/signals-api/layoffs/sample-requests.md).

# Intellizence Layoffs API Sample Requests

## Layoffs API Sample Requests

Use these sample API requests to retrieve layoff, downsizing, workforce reduction, plant closure, furlough, and job cut records from the Intellizence Layoffs Dataset.

These examples show common ways to filter layoff records by date, company domain, industry, company location, layoff location, company type, ticker, layoff type, layoff reason, and limit.

{% hint style="info" %}
All request parameters are optional. You can use a single filter or combine multiple filters based on your use case.
{% endhint %}

***

### Endpoint

```http
POST https://connect.intellizence.com/api/dataset/layoff
```

### Authentication

Include your API key in the request header.

```http
x-api-key: YOUR_API_KEY
```

### Content Type

```http
Content-Type: application/json
```

***

## Sample API Requests

### 1. Get Daily Updated Records

Use `dateType: "LAST-MODIFIED"` to retrieve records that were created or updated on a specific date.

This is recommended for daily syncs, alerts, enrichment workflows, and automated data pipelines.

#### Request Body

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2026-03-03",
  "limit": 5
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "LAST-MODIFIED",
    "date": "2026-03-03",
    "limit": 5
  }'
```

***

### 2. Get Layoffs Announced on a Specific Date

Use `dateType: "ANNOUNCED"` and `date` to retrieve layoff records announced on a specific date.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "date": "2026-03-03",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "date": "2026-03-03",
    "limit": 10
  }'
```

***

### 3. Get Layoffs Within a Date Range

Use `startDate` and `endDate` to retrieve layoffs announced during a specific period.

The Intellizence Layoffs Dataset contains data beginning from `2020-01-01`.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2026-03-01",
  "endDate": "2026-03-31",
  "limit": 25
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2026-03-01",
    "endDate": "2026-03-31",
    "limit": 25
  }'
```

***

### 4. Search by Company Domain

Use `companyDomain` to retrieve layoff records for a specific company website domain.

This is recommended for CRM enrichment, account matching, risk monitoring, data pipelines, and workflow automation because domains are usually more precise than company names.

#### Request Body

```json
{
  "companyDomain": "dteenergy.com",
  "limit": 10
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyDomain": "dteenergy.com",
    "limit": 10
  }'
```

***

### 5. Search by Company Industry

Use `companyIndustry` to retrieve layoff records for companies in one or more industries.

This is useful for market research, sector monitoring, risk analysis, workforce trend analysis, and investment research.

#### Request Body

```json
{
  "companyIndustry": [
    "technology",
    "retail"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyIndustry": [
      "technology",
      "retail"
    ],
    "limit": 20
  }'
```

***

### 6. Search by Company Location

Use `companyLocation` to find layoff records for companies headquartered in a specific city, state, province, country, or region.

#### Request Body

```json
{
  "companyLocation": "Detroit,Michigan,United States of America",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "companyLocation": "Detroit,Michigan,United States of America",
    "limit": 20
  }'
```

***

### 7. Search by Layoff Location

Use `layoffLocation` to find layoff events announced for a specific location.

This is useful when you want to track workforce reductions by plant, office, city, state, province, country, or region.

#### Request Body

```json
{
  "layoffLocation": "Superior,Wisconsin,United States of America",
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "layoffLocation": "Superior,Wisconsin,United States of America",
    "limit": 20
  }'
```

***

### 8. Search by Layoff Type

Use `layoffType` to retrieve layoffs by event type.

Examples include `Downsizing/Layoff`, `Furlough/Temporary`, `Hiring Freeze`, `Permanent Plant Closure`, `Temporary Plant Closure`, `Voluntary Retirement`, `Voluntary Separation Program`, and `Other`.

#### Request Body

```json
{
  "layoffType": [
    "Downsizing/Layoff",
    "Permanent Plant Closure"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "layoffType": [
      "Downsizing/Layoff",
      "Permanent Plant Closure"
    ],
    "limit": 20
  }'
```

***

### 9. Search by Layoff Reason

Use `layoffReason` to retrieve layoffs by the reason mentioned in the source.

Examples include `Restructuring`, `Cost-cutting`, `M&A`, `Automation`, `Business Closure`, `Relocation`, `Bankruptcy`, `Financial Distress`, `AI Automation`, and `Not Specified`.

#### Request Body

```json
{
  "layoffReason": [
    "Restructuring",
    "Cost-cutting"
  ],
  "limit": 20
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "layoffReason": [
      "Restructuring",
      "Cost-cutting"
    ],
    "limit": 20
  }'
```

***

### 10. Use Multiple Filters Together

Combine filters to narrow results by date range, industry, company type, layoff type, layoff reason, and location.

#### Request Body

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31",
  "companyIndustry": [
    "technology"
  ],
  "companyType": [
    "Public"
  ],
  "layoffType": [
    "Downsizing/Layoff"
  ],
  "layoffReason": [
    "Restructuring",
    "Cost-cutting"
  ],
  "layoffLocation": "United States of America",
  "limit": 50
}
```

#### cURL Example

```bash
curl --request POST \
  --url https://connect.intellizence.com/api/dataset/layoff \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --data '{
    "dateType": "ANNOUNCED",
    "startDate": "2026-01-01",
    "endDate": "2026-03-31",
    "companyIndustry": [
      "technology"
    ],
    "companyType": [
      "Public"
    ],
    "layoffType": [
      "Downsizing/Layoff"
    ],
    "layoffReason": [
      "Restructuring",
      "Cost-cutting"
    ],
    "layoffLocation": "United States of America",
    "limit": 50
  }'
```

***

## Use Case Examples

### 1. Daily Data Sync

Use this example when you want to pull newly added or updated layoff records into your application, database, CRM, dashboard, or analytics workflow.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2026-03-03",
  "limit": 100
}
```

#### Best For

* Data pipelines
* Daily refreshes
* Internal dashboards
* Alerts and workflow automation
* CRM and data warehouse enrichment

***

### 2. CRM or Account Risk Enrichment

Use this example to check whether a company in your CRM has recent layoff activity.

#### Recommended Filters

```json
{
  "companyDomain": "dteenergy.com",
  "dateType": "LAST-MODIFIED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31",
  "limit": 10
}
```

#### Best For

* CRM enrichment
* Account risk scoring
* Customer health monitoring
* Sales and customer success workflows
* Renewal and churn risk monitoring

***

### 3. Sector Workforce Trend Analysis

Use this example to track layoff activity across a specific industry.

#### Recommended Filters

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31",
  "companyIndustry": [
    "technology"
  ],
  "limit": 50
}
```

#### Best For

* Workforce trend analysis
* Market research
* Sector monitoring
* Investment research
* Competitive intelligence

***

### 4. WARN and Plant Closure Monitoring

Use this example to monitor plant closures, facility shutdowns, and location-specific workforce reductions.

#### Recommended Filters

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31",
  "layoffType": [
    "Permanent Plant Closure",
    "Temporary Plant Closure"
  ],
  "layoffLocation": "United States of America",
  "limit": 50
}
```

#### Best For

* WARN notice monitoring
* Plant closure tracking
* Economic development research
* Supply chain risk monitoring
* Location-based workforce analysis

***

### 5. Sales and Customer Success Monitoring

Use this example to identify accounts going through restructuring, cost-cutting, or workforce reductions.

#### Recommended Filters

```json
{
  "dateType": "LAST-MODIFIED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31",
  "companyIndustry": [
    "technology"
  ],
  "layoffReason": [
    "Restructuring",
    "Cost-cutting",
    "Financial Distress"
  ],
  "limit": 25
}
```

#### Best For

* Account prioritization
* Customer risk monitoring
* Renewal risk detection
* Signal-based outreach
* Churn and downsell risk workflows

***

## Recommended Use Cases

| Use Case                              | Recommended Filters                                 |
| ------------------------------------- | --------------------------------------------------- |
| Daily data sync                       | `dateType`, `date`, `limit`                         |
| CRM or account risk enrichment        | `companyDomain`, `dateType`, `startDate`, `endDate` |
| Sector workforce trend analysis       | `companyIndustry`, date range, `limit`              |
| WARN and plant closure monitoring     | `layoffType`, `layoffLocation`, date range          |
| Sales and customer success monitoring | `companyIndustry`, `layoffReason`, date range       |

***

## Best Practices

### Prefer company domain for company matching

For CRM enrichment, data pipelines, account matching, and automated workflows, use `companyDomain` when available.

Company domains are usually more precise than company names and help reduce duplicate or ambiguous matches.

```json
{
  "companyDomain": "dteenergy.com",
  "limit": 10
}
```

### Use company name for manual lookup

You can also use `companyName` to search for layoff records by company name.

Company name search is useful for manual lookup, but for automated workflows, CRM enrichment, and account matching, use `companyDomain` when available.

```json
{
  "companyName": "DTE Energy",
  "limit": 10
}
```

### Use ticker for public company monitoring

For public companies, use `companyTicker` when you want to search by stock ticker.

```json
{
  "companyTicker": "DTE",
  "limit": 10
}
```

### Use `LAST-MODIFIED` for daily syncs

For recurring syncs, alerts, and automated workflows, use `LAST-MODIFIED`.

```json
{
  "dateType": "LAST-MODIFIED",
  "date": "2026-03-03"
}
```

This helps retrieve records that were newly added or updated on that date.

### Use `ANNOUNCED` for event-date research

For research based on when a layoff was announced, use `ANNOUNCED`.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31"
}
```

### Use company location for headquarters-based analysis

Use `companyLocation` when you want to filter by where the company is headquartered.

```json
{
  "companyLocation": "Detroit,Michigan,United States of America",
  "limit": 20
}
```

### Use layoff location for event-location analysis

Use `layoffLocation` when you want to filter by where the layoff, closure, or workforce reduction occurred.

```json
{
  "layoffLocation": "Superior,Wisconsin,United States of America",
  "limit": 20
}
```

### Use layoff type to classify workforce events

Use `layoffType` to distinguish between layoffs, furloughs, hiring freezes, plant closures, and voluntary separation programs.

```json
{
  "layoffType": [
    "Downsizing/Layoff",
    "Permanent Plant Closure"
  ],
  "limit": 25
}
```

### Use layoff reason for risk and trend analysis

Use `layoffReason` to analyze why workforce reductions are happening.

```json
{
  "layoffReason": [
    "Restructuring",
    "Cost-cutting",
    "Financial Distress"
  ],
  "limit": 25
}
```

### Use `limit` to control result size

The default limit is `100` records if no limit is provided.

```json
{
  "limit": 100
}
```

### Combine filters for more precise results

You can combine multiple filters in a single request to narrow your results.

```json
{
  "dateType": "ANNOUNCED",
  "startDate": "2026-01-01",
  "endDate": "2026-03-31",
  "companyIndustry": [
    "technology"
  ],
  "companyType": [
    "Public"
  ],
  "layoffReason": [
    "Restructuring",
    "Cost-cutting"
  ],
  "limit": 50
}
```

***

## Notes

* All parameters are optional.
* Dates should be provided in `YYYY-MM-DD` format.
* The Intellizence Layoffs Dataset contains data beginning from `2020-01-01`.
* Use `LAST-MODIFIED` when you want newly added or updated records.
* Use `ANNOUNCED` when you want records based on the layoff announcement date.
* Use `companyDomain` for CRM matching, account enrichment, risk monitoring, and workflow automation.
* Use `companyName` for manual lookup when the company domain is not available.
* Use `companyTicker` for public company monitoring.
* Use `companyLocation` for headquarters-based filtering.
* Use `layoffLocation` for event-location filtering.
* Use `layoffType` to filter by workforce event type.
* Use `layoffReason` to filter by the reason mentioned in the source.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.intellizence.com/signals-api/layoffs/sample-requests.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.