NEVER TRAINED ON · PRIVATE BY DEFAULT · BUILT BY MOZILLA

GITHUB

Schema library jobs

Return a layoff-event record from a public page.

Pass this JSON Schema and a public source URL to/extract/json. Structure public reports and announcements with source attribution.

tabstack.ai/pricing

TEXT

MARKDOWN

LINKS

extract.tsTypeScript
const res = await client.extract.json({
  url: 'https://example.com/pricing',
  json_schema: {
    type: 'object',
    properties: {
      plan: { type: 'string' },
      price: { type: 'number' },
    },
  },
})

What it captures

Fields in this layoff-event record.

Schema for company layoff and workforce reduction event records.

FieldTypeWhat it holds
company_namestring, requiredName of the company conducting the layoff.
company_domainstringWebsite domain of the company.
company_industrystringIndustry sector of the company.
headcount_affectednumberNumber of employees affected by the layoff.
headcount_affected_pctnumberPercentage of total workforce affected.
affected_departmentsarrayDepartments or teams affected by the layoff.
affected_locationsarrayOffice locations affected by the layoff.
announcement_datestring, requiredDate the layoff was publicly announced.
effective_datestringDate the layoffs took or take effect.
layoff_typestringStated reason or type of layoff.
severance_weeksnumberNumber of weeks of severance pay offered.
rehire_eligiblebooleanWhether laid-off employees are eligible for rehire.
source_typestringType of source for the layoff information.
ceo_statementstringStatement or message from the CEO about the layoff.
page_titlestringTitle of the source page. Tabstack auto-fills this from page metadata when left empty.
faviconstringFavicon URL of the source page. Tabstack auto-fills this from page metadata when left empty.

Example

Inspect and validate the response shape.

The example below is generated from the schema to demonstrate its structure. Edit the object or paste a real response to validate it in your browser.

What it checks

Pass or fail, and the first reason why.

Whether the text parses as JSON, whether the top level is an object, and whether each field the schema requires is present at the declared type. A null is allowed anywhere. Every key you ask for is present. A field the page does not state can come back null, empty, a placeholder number, or a guessed value. Validate values, not just keys.

Example data, not a live response.

Usage

Send the schema with your source URL.

The schema travels with the request rather than living on your account, so the same call can send a trimmed version for one page and the full one for another. Every key you ask for is present. A field the page does not state can come back null, empty, a placeholder number, or a guessed value. Validate values, not just keys.

layoff.tsTypeScript
import schema from './layoff-event.json'

const res = await client.extract.json({
  url: 'https://example.com/pricing',
  json_schema: schema,
})

Adaptation

Make the schema match your application.

The schema is a starting point, not a guarantee that every source page contains every field. Three things are worth doing before you write one into your system, and the schema-authoring guide covers the rest.

Remove what you do not need

A shorter schema is a smaller response and fewer fields to handle.

Describe the ambiguous ones

A description tells Extract what to look for when a label could mean two things.

Validate before you store

Check the returned object against the schema rather than trusting it.

Related

Related schemas

Other schemas in this category.

START FREE

Try this schema on a public page.

Start with 10,000 free credits. No credit card required.

curl -X POST https://api.tabstack.ai/v1/extract/json -H "Authorization: Bearer $TABSTACK_API_KEY" -d '{"url":"...","json_schema":{...}}'