Get event fields

GET

api

events_info

get_event_fields

curl --request GET \
  --url https://events.newscatcherapi.xyz/api/events_info/get_event_fields \
  --header 'x-api-token: <api-key>'

{
  "message": "Success",
  "count": 12,
  "fields": {
    "company_name": {
      "type": "String",
      "usage_example": {
        "company_name": "Tesla"
      }
    },
    "event_date": {
      "type": "Date",
      "usage_example": {
        "event_date": {
          "lte": "now",
          "gte": "now-30d"
        }
      }
    },
    "extraction_date": {
      "type": "Date",
      "usage_example": {
        "event_date": {
          "lte": "now",
          "gte": "now-30d"
        }
      }
    },
    "layoff.how_much_related": {
      "type": "String",
      "usage_example": {
        "company_name": "Tesla"
      }
    },
    "layoff.is_relevant_for_real_estate": "true",
    "layoff.layoff_reason": {
      "type": "String",
      "usage_example": {
        "company_name": "Tesla"
      }
    },
    "layoff.location": {
      "country": "<string>",
      "city": "<string>",
      "raw_location": "<string>",
      "county": "<string>",
      "state": "<string>"
    },
    "layoff.max_number_of_people_laid_off": {
      "type": "Number",
      "usage_example": {
        "number_of_people_laid_off": {
          "gte": 100,
          "lte": 1000
        }
      }
    },
    "layoff.min_number_of_people_laid_off": {
      "type": "Number",
      "usage_example": {
        "number_of_people_laid_off": {
          "gte": 100,
          "lte": 1000
        }
      }
    },
    "layoff.number_of_people_laid_off": {
      "type": "Number",
      "usage_example": {
        "number_of_people_laid_off": {
          "gte": 100,
          "lte": 1000
        }
      }
    },
    "layoff.percentage_of_people_laid_off": {
      "type": "Number",
      "usage_example": {
        "number_of_people_laid_off": {
          "gte": 100,
          "lte": 1000
        }
      }
    },
    "layoff.summary": {
      "type": "String",
      "usage_example": {
        "company_name": "Tesla"
      }
    }
  }
}

Authorizations

x-api-token

string

header

required

API Key to authenticate requests.

To access the API, include your API key in the x-api-token header. To obtain your API key, complete the form or contact us directly.

Query Parameters

event_type

string

required

Type of event to get fields for

Response

200

application/json

Available fields for the specified event type

message

string

required

Status message indicating success or providing additional context

Example:

"Success"

count

integer

required

Total number of available fields returned

Example:

12

fields

object

required

Map of field names to their type definitions and usage examples

fields.company_name

object

required

Name of the company that conducted the layoff.

fields.company_name.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.company_name.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.event_date

object

required

Date when the layoff occurred.

fields.event_date.type

enum<string>

required

Indicates this field accepts date values

Available options:

Date

fields.event_date.usage_example

object

required

Shows how to use date ranges in search queries. Supports both absolute (YYYY-MM-DD) and relative (now-30d) date formats.

Example:

{
  "event_date": { "lte": "now", "gte": "now-30d" }
}

fields.extraction_date

object

required

Date when the event was extracted from news sources.

fields.extraction_date.type

enum<string>

required

Indicates this field accepts date values

Available options:

Date

fields.extraction_date.usage_example

object

required

Shows how to use date ranges in search queries. Supports both absolute (YYYY-MM-DD) and relative (now-30d) date formats.

Example:

{
  "event_date": { "lte": "now", "gte": "now-30d" }
}

Relevance rating of the layoff event.

Indicates this field accepts string values

Available options:

String

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.layoff.is_relevant_for_real_estate

enum<string>

Indicates if the layoff impacts real estate market.

Available options:

true,

false

fields.layoff.layoff_reason

object

Stated reason for the layoff.

fields.layoff.layoff_reason.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.layoff.layoff_reason.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.layoff.location

object

Location where the layoff occurred.

fields.layoff.max_number_of_people_laid_off

object

Maximum number of employees affected in a range.

fields.layoff.max_number_of_people_laid_off.type

enum<string>

required

Indicates this field accepts numeric values

Available options:

Number

fields.layoff.max_number_of_people_laid_off.usage_example

object

required

Shows how to use numeric ranges in search queries

Example:

{
  "number_of_people_laid_off": { "gte": 100, "lte": 1000 }
}

fields.layoff.min_number_of_people_laid_off

object

Minimum number of employees affected in a range.

fields.layoff.min_number_of_people_laid_off.type

enum<string>

required

Indicates this field accepts numeric values

Available options:

Number

fields.layoff.min_number_of_people_laid_off.usage_example

object

required

Shows how to use numeric ranges in search queries

Example:

{
  "number_of_people_laid_off": { "gte": 100, "lte": 1000 }
}

fields.layoff.number_of_people_laid_off

object

Exact number of employees affected.

fields.layoff.number_of_people_laid_off.type

enum<string>

required

Indicates this field accepts numeric values

Available options:

Number

fields.layoff.number_of_people_laid_off.usage_example

object

required

Shows how to use numeric ranges in search queries

Example:

{
  "number_of_people_laid_off": { "gte": 100, "lte": 1000 }
}

fields.layoff.percentage_of_people_laid_off

object

Percentage of workforce affected.

fields.layoff.percentage_of_people_laid_off.type

enum<string>

required

Indicates this field accepts numeric values

Available options:

Number

fields.layoff.percentage_of_people_laid_off.usage_example

object

required

Shows how to use numeric ranges in search queries

Example:

{
  "number_of_people_laid_off": { "gte": 100, "lte": 1000 }
}

fields.layoff.summary

object

Summary text of the layoff event.

fields.layoff.summary.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.layoff.summary.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

message

string

required

Status message indicating success or providing additional context

Example:

"Success"

count

integer

required

Total number of available fields returned

Example:

12

fields

object

required

Map of field names to their type definitions and usage examples

fields.company_name

object

required

Name of the company that conducted the layoff.

fields.company_name.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.company_name.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.event_date

object

required

Date when the layoff occurred.

fields.event_date.type

enum<string>

required

Indicates this field accepts date values

Available options:

Date

fields.event_date.usage_example

object

required

Shows how to use date ranges in search queries. Supports both absolute (YYYY-MM-DD) and relative (now-30d) date formats.

Example:

{
  "event_date": { "lte": "now", "gte": "now-30d" }
}

fields.extraction_date

object

required

Date when the event was extracted from news sources.

fields.extraction_date.type

enum<string>

required

Indicates this field accepts date values

Available options:

Date

fields.extraction_date.usage_example

object

required

Shows how to use date ranges in search queries. Supports both absolute (YYYY-MM-DD) and relative (now-30d) date formats.

Example:

{
  "event_date": { "lte": "now", "gte": "now-30d" }
}

Relevance rating of the layoff event.

Indicates this field accepts string values

Available options:

String

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.layoff.is_relevant_for_real_estate

enum<string>

Indicates if the layoff impacts real estate market.

Available options:

true,

false

fields.layoff.layoff_reason

object

Stated reason for the layoff.

fields.layoff.layoff_reason.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.layoff.layoff_reason.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.layoff.location

object

Location where the layoff occurred.

fields.layoff.max_number_of_people_laid_off

object

Maximum number of employees affected in a range.

fields.layoff.max_number_of_people_laid_off.type

enum<string>

required

Indicates this field accepts numeric values

Available options:

Number

fields.layoff.max_number_of_people_laid_off.usage_example

object

required

Shows how to use numeric ranges in search queries

Example:

{
  "number_of_people_laid_off": { "gte": 100, "lte": 1000 }
}

fields.layoff.min_number_of_people_laid_off

object

Minimum number of employees affected in a range.

fields.layoff.min_number_of_people_laid_off.type

enum<string>

required

Indicates this field accepts numeric values

Available options:

Number

fields.layoff.min_number_of_people_laid_off.usage_example

object

required

Shows how to use numeric ranges in search queries

Example:

{
  "number_of_people_laid_off": { "gte": 100, "lte": 1000 }
}

fields.layoff.number_of_people_laid_off

object

Exact number of employees affected.

fields.layoff.number_of_people_laid_off.type

enum<string>

required

Indicates this field accepts numeric values

Available options:

Number

fields.layoff.number_of_people_laid_off.usage_example

object

required

Shows how to use numeric ranges in search queries

Example:

{
  "number_of_people_laid_off": { "gte": 100, "lte": 1000 }
}

fields.layoff.percentage_of_people_laid_off

object

Percentage of workforce affected.

fields.layoff.percentage_of_people_laid_off.type

enum<string>

required

Indicates this field accepts numeric values

Available options:

Number

fields.layoff.percentage_of_people_laid_off.usage_example

object

required

Shows how to use numeric ranges in search queries

Example:

{
  "number_of_people_laid_off": { "gte": 100, "lte": 1000 }
}

fields.layoff.summary

object

Summary text of the layoff event.

fields.layoff.summary.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.layoff.summary.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

message

string

required

Status message indicating success or providing additional context

Example:

"Success"

count

integer

required

Total number of available fields returned

Example:

12

fields

object

required

Map of field names to their type definitions and usage examples

fields.company_name

object

required

Name of the company affected by the data breach.

fields.company_name.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.company_name.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.event_date

object

required

Date when the data breach occurred.

fields.event_date.type

enum<string>

required

Indicates this field accepts date values

Available options:

Date

fields.event_date.usage_example

object

required

Shows how to use date ranges in search queries. Supports both absolute (YYYY-MM-DD) and relative (now-30d) date formats.

Example:

{
  "event_date": { "lte": "now", "gte": "now-30d" }
}

fields.extraction_date

object

required

Date when the event was extracted from news sources.

fields.extraction_date.type

enum<string>

required

Indicates this field accepts date values

Available options:

Date

fields.extraction_date.usage_example

object

required

Shows how to use date ranges in search queries. Supports both absolute (YYYY-MM-DD) and relative (now-30d) date formats.

Example:

{
  "event_date": { "lte": "now", "gte": "now-30d" }
}

fields.data_breach.data

object

Type of data that was compromised.

fields.data_breach.data.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.data_breach.data.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.data_breach.data_type

object

Classification of compromised data.

fields.data_breach.data_type.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.data_breach.data_type.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.data_breach.impacted

object

Type of entities affected by the breach.

fields.data_breach.impacted.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.data_breach.impacted.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.data_breach.summary

object

Summary text of the data breach event.

fields.data_breach.summary.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.data_breach.summary.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.data_breach.title

object

Title of the data breach event.

fields.data_breach.title.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.data_breach.title.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

message

string

required

Status message indicating success or providing additional context

Example:

"Success"

count

integer

required

Total number of available fields returned

Example:

12

fields

object

required

Map of field names to their type definitions and usage examples

fields.company_name

object

required

Name of the company that received funding.

fields.company_name.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.company_name.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.event_date

object

required

Date when the fundraising occurred.

fields.event_date.type

enum<string>

required

Indicates this field accepts date values

Available options:

Date

fields.event_date.usage_example

object

required

Shows how to use date ranges in search queries. Supports both absolute (YYYY-MM-DD) and relative (now-30d) date formats.

Example:

{
  "event_date": { "lte": "now", "gte": "now-30d" }
}

fields.extraction_date

object

required

Date when the event was extracted from news sources.

fields.extraction_date.type

enum<string>

required

Indicates this field accepts date values

Available options:

Date

fields.extraction_date.usage_example

object

required

Shows how to use date ranges in search queries. Supports both absolute (YYYY-MM-DD) and relative (now-30d) date formats.

Example:

{
  "event_date": { "lte": "now", "gte": "now-30d" }
}

fields.fundraising.amount

object

Amount of funding raised.

fields.fundraising.amount.type

enum<string>

required

Indicates this field accepts numeric values

Available options:

Number

fields.fundraising.amount.usage_example

object

required

Shows how to use numeric ranges in search queries

Example:

{
  "number_of_people_laid_off": { "gte": 100, "lte": 1000 }
}

fields.fundraising.company_description

object

Description of the funded company.

fields.fundraising.company_description.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.fundraising.company_description.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.fundraising.company_legal_name

object

Legal name of the funded company.

fields.fundraising.company_legal_name.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.fundraising.company_legal_name.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.fundraising.currency

object

Currency of the funding amount.

fields.fundraising.currency.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.fundraising.currency.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.fundraising.founders

object

Names of company founders.

fields.fundraising.founders.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.fundraising.founders.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.fundraising.funding_type

object

Type of funding round.

fields.fundraising.funding_type.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.fundraising.funding_type.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.fundraising.industry

object

Industry of the funded company.

fields.fundraising.industry.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.fundraising.industry.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.fundraising.investors

object

Names of investors.

fields.fundraising.investors.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.fundraising.investors.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.fundraising.valuation

object

Company valuation at the time of funding.

fields.fundraising.valuation.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.fundraising.valuation.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

message

string

required

Status message indicating success or providing additional context

Example:

"Success"

count

integer

required

Total number of available fields returned

Example:

12

fields

object

required

Map of field names to their type definitions and usage examples

fields.company_name

object

required

Name of the company related to the tariff event.

fields.company_name.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.company_name.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.event_date

object

required

Date when the tariff event occurred.

fields.event_date.type

enum<string>

required

Indicates this field accepts date values

Available options:

Date

fields.event_date.usage_example

object

required

Shows how to use date ranges in search queries. Supports both absolute (YYYY-MM-DD) and relative (now-30d) date formats.

Example:

{
  "event_date": { "lte": "now", "gte": "now-30d" }
}

fields.extraction_date

object

required

Date when the event was extracted from news sources.

fields.extraction_date.type

enum<string>

required

Indicates this field accepts date values

Available options:

Date

fields.extraction_date.usage_example

object

required

Shows how to use date ranges in search queries. Supports both absolute (YYYY-MM-DD) and relative (now-30d) date formats.

Example:

{
  "event_date": { "lte": "now", "gte": "now-30d" }
}

fields.tariffs_v2.affected_industries

object

Industries affected by the tariff or trade measure.

fields.tariffs_v2.affected_industries.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.affected_industries.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.affected_products

object

Specific products affected by the tariff or trade measure.

fields.tariffs_v2.affected_products.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.affected_products.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.announcement_date

object

Date when the tariff or trade measure was announced.

fields.tariffs_v2.announcement_date.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.announcement_date.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.estimated_trade_value

object

The estimated value of trade affected by the measure.

fields.tariffs_v2.estimated_trade_value.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.estimated_trade_value.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.hs_product_categories

object

Harmonized System (HS) sections of products affected by the tariff.

fields.tariffs_v2.hs_product_categories.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.hs_product_categories.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.implementation_date

object

Date when the tariff or trade measure will be or was implemented.

fields.tariffs_v2.implementation_date.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.implementation_date.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.imposing_country_code

object

The ISO 3166-1 alpha-2 code of the country implementing the tariff.

fields.tariffs_v2.imposing_country_code.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.imposing_country_code.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.imposing_country_name

object

The name of the country implementing the tariff.

fields.tariffs_v2.imposing_country_name.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.imposing_country_name.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.main_tariff_rate

object

The most significant tariff rate mentioned.

fields.tariffs_v2.main_tariff_rate.type

enum<string>

required

Indicates this field accepts numeric values

Available options:

Number

fields.tariffs_v2.main_tariff_rate.usage_example

object

required

Shows how to use numeric ranges in search queries

Example:

{
  "number_of_people_laid_off": { "gte": 100, "lte": 1000 }
}

fields.tariffs_v2.measure_type

object

Type of trade measure being implemented.

fields.tariffs_v2.measure_type.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.measure_type.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.policy_objective

object

Stated policy objective for implementing the tariff.

fields.tariffs_v2.policy_objective.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.policy_objective.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.previous_tariff_rate

object

The tariff rates before this change.

fields.tariffs_v2.previous_tariff_rate.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.previous_tariff_rate.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.relevance_score

object

Rating of how directly the article addresses specific tariff announcements.

fields.tariffs_v2.relevance_score.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.relevance_score.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.summary

object

A comprehensive summary of the tariff announcement or change.

fields.tariffs_v2.summary.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.summary.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.targeted_country_codes

object

ISO 3166-1 alpha-2 codes for countries targeted by the tariff.

fields.tariffs_v2.targeted_country_codes.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.targeted_country_codes.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.targeted_country_names

object

Names of countries targeted by the tariff.

fields.tariffs_v2.targeted_country_names.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.targeted_country_names.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.tariff_rates

object

List of tariff rate descriptions.

fields.tariffs_v2.tariff_rates.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.tariff_rates.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

fields.tariffs_v2.trigger_event

object

Description of what triggered the retaliatory measure.

fields.tariffs_v2.trigger_event.type

enum<string>

required

Indicates this field accepts string values

Available options:

String

fields.tariffs_v2.trigger_event.usage_example

object

required

Shows how to use this field in search queries

Example:

{ "company_name": "Tesla" }

Was this page helpful?

Suggest edits Raise issue

Tariffs Search for events

curl --request GET \
  --url https://events.newscatcherapi.xyz/api/events_info/get_event_fields \
  --header 'x-api-token: <api-key>'

{
  "message": "Success",
  "count": 12,
  "fields": {
    "company_name": {
      "type": "String",
      "usage_example": {
        "company_name": "Tesla"
      }
    },
    "event_date": {
      "type": "Date",
      "usage_example": {
        "event_date": {
          "lte": "now",
          "gte": "now-30d"
        }
      }
    },
    "extraction_date": {
      "type": "Date",
      "usage_example": {
        "event_date": {
          "lte": "now",
          "gte": "now-30d"
        }
      }
    },
    "layoff.how_much_related": {
      "type": "String",
      "usage_example": {
        "company_name": "Tesla"
      }
    },
    "layoff.is_relevant_for_real_estate": "true",
    "layoff.layoff_reason": {
      "type": "String",
      "usage_example": {
        "company_name": "Tesla"
      }
    },
    "layoff.location": {
      "country": "<string>",
      "city": "<string>",
      "raw_location": "<string>",
      "county": "<string>",
      "state": "<string>"
    },
    "layoff.max_number_of_people_laid_off": {
      "type": "Number",
      "usage_example": {
        "number_of_people_laid_off": {
          "gte": 100,
          "lte": 1000
        }
      }
    },
    "layoff.min_number_of_people_laid_off": {
      "type": "Number",
      "usage_example": {
        "number_of_people_laid_off": {
          "gte": 100,
          "lte": 1000
        }
      }
    },
    "layoff.number_of_people_laid_off": {
      "type": "Number",
      "usage_example": {
        "number_of_people_laid_off": {
          "gte": 100,
          "lte": 1000
        }
      }
    },
    "layoff.percentage_of_people_laid_off": {
      "type": "Number",
      "usage_example": {
        "number_of_people_laid_off": {
          "gte": 100,
          "lte": 1000
        }
      }
    },
    "layoff.summary": {
      "type": "String",
      "usage_example": {
        "company_name": "Tesla"
      }
    }
  }
}

Overview

How to

Event types

Endpoints

Authorizations

Query Parameters

Response