LiveEstablished
Job opening posted
JOB_OPENING_POSTEDA vacancy appears on the careers page an organization runs. Each listing becomes one event, built from the listing’s structured data rather than extracted from article text.
evinor.ai/events/new-job-opening
Create a sensor for this type→/ schema · roles
| ROLE | CODE_NAME | TYPE | REPEATS | DESCRIPTION |
|---|---|---|---|---|
| Employer | EMPLOYER | NAMED_ENTITY | — | The organization that is hiring. |
| Job Posting Reference | JOB_POSTING_REFERENCE | NONE | — | An opaque identifier for the listing, stable across deliveries of the same opening. |
| Job Title | JOB_TITLE | NONE | — | The position title exactly as the board shows it. |
| Department | DEPARTMENT | NONE | — | The team or function label the board attaches to the listing. Absent when the board gives none. |
| Seniority | SENIORITY | CATEGORICAL | — | How senior the role is, delivered as an uppercase token from a fixed vocabulary. |
| Employment Type | EMPLOYMENT_TYPE | CATEGORICAL | — | The employment arrangement for the role, delivered as an uppercase token from a fixed vocabulary. Absent when the board gives none. |
| Workplace Type | WORKPLACE_TYPE | CATEGORICAL | — | Whether the position is on-site, hybrid or remote, delivered as an uppercase token from a fixed vocabulary. |
| Job Location | JOB_LOCATION | NAMED_ENTITY | yes | A location the listing gives for the role. A listing with several locations carries several entries. |
| Salary Minimum | SALARY_MIN | CURRENCY | — | The low end of the pay range when the board publishes one in structured form. |
| Salary Maximum | SALARY_MAX | CURRENCY | — | The high end of the pay range when the board publishes one in structured form. |
| Salary Period | SALARY_PERIOD | CATEGORICAL | — | The interval the pay range is quoted over, such as per year or per hour, delivered as an uppercase token. Present whenever a pay range is. |
/ example event
Northwind Robotics posted a new Senior Engineer opening in Toronto.
- Employer
- Northwind Robotics
- Job Title
- Senior Engineer
- Job Location
- Toronto
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": "<Job opening posted event type id>", "lookback_days": 30 }'import { Evinor } from '@evinor/sdk'; const evinor = new Evinor(); // reads EVINOR_API_KEY for await (const event of evinor.events.searchAll({ event_type_id: '<Job opening posted event type id>', lookback_days: 30,})) { console.log(event.first_report_date, event.sentence);}// MCP tool — same filter vocabulary as the REST APIsearch_events{ "event_type_id": "<Job opening posted event type id>", "lookback_days": 30}/ publish it first-hand
Know about a job opening posted before it’s reported? File it as a structured report with POST /v1/reports, a value per role.
EMPLOYERJOB_POSTING_REFERENCEJOB_TITLEDEPARTMENTSENIORITYEMPLOYMENT_TYPEWORKPLACE_TYPEJOB_LOCATIONSALARY_MINSALARY_MAXSALARY_PERIOD
Publish to Evinor →/ notes
Established type. Webhook and sensor payloads carry confidence.band (HIGH / MEDIUM / LOW) when available; search results do not.
Need a type we don’t cover?Request an event type →Know it first?Publish events of this kind first-hand →
Read the catalog from the APIGET /v1/event-types