LiveEstablished

Layoff

LAYOFF

A company lays off employees.

Create a sensor for this type→

/ schema · roles

5 roles
ROLECODE_NAMETYPEREPEATSDESCRIPTION
Company NameCOMPANY_NAMENAMED_ENTITY—The employer reducing its headcount.
Number of Employees AffectedAFFECTED_EMPLOYEES_COUNTNUMBER—How many roles were eliminated.
Percentage of Workforce AffectedPERCENTAGE_OF_WORKFORCE_AFFECTEDNUMBER—Share of total staff let go, as a percentage.
Reason for LayoffANNOUNCED_REASONNONE—The publicly stated rationale for the cuts.
Category of Employees AffectedCATEGORY_OF_EMPLOYEES_AFFECTEDNONE—Which team or function bore the cuts, such as sales.

/ example event

Example data

Quillmark laid off 120 employees, about 8% of its workforce, citing a restructuring.

Company Name
Quillmark
Number of Employees Affected
120
Percentage of Workforce Affected
8
Reason for Layoff
restructuring

Delivered as payload.details; role codes are listed in the API reference.

/ use it

curl https://api.evinor.ai/v1/events/search \  -H "Authorization: Bearer $EVINOR_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "event_type_id": "<Layoff event type id>",    "lookback_days": 30  }'

/ publish it first-hand

Know about a layoff before it’s reported? File it as a structured report with POST /v1/reports, a value per role.

COMPANY_NAMEAFFECTED_EMPLOYEES_COUNTPERCENTAGE_OF_WORKFORCE_AFFECTEDANNOUNCED_REASONCATEGORY_OF_EMPLOYEES_AFFECTED
Publish to Evinor →

/ notes

Established type. Webhook and sensor payloads carry confidence.band (HIGH / MEDIUM / LOW) when available; search results do not.