Schema library jobs

Return a hiring-velocity record from a public page.

Pass this JSON Schema and a public source URL to/extract/json. Structure observable public hiring signals for analysis.

Use this schema The JSON file

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' },
    },
  },
})

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

tabstack extract json https://example.com/pricing \
  --schema '{"type":"object","properties":{"plan":{"type":"string"},"price":{"type":"number"}}}'

What it captures

Fields in this hiring-velocity record.

Schema for tracking a company's open job roles and hiring pace over time.

Field	Type	What it holds
`company_name`	string, required	Name of the company.
`company_domain`	string, required	Website domain of the company.
`snapshot_date`	string, required	Date this hiring snapshot was captured.
`total_open_roles`	number, required	Total number of currently open job listings.
`roles_by_department`	object	Breakdown of open roles by department.
`roles_by_seniority`	object	Breakdown of open roles by seniority level.
`remote_roles_count`	number	Number of roles that are remote.
`remote_roles_pct`	number	Percentage of open roles that are remote.
`new_roles_last_30d`	number	Number of new roles posted in the last 30 days.
`closed_roles_last_30d`	number	Number of roles closed or filled in the last 30 days.
`top_hiring_titles`	array	Most common or featured job titles currently hiring.
`source_platform`	string	Platform from which this data was gathered (e.g., LinkedIn, Greenhouse).
`page_title`	string	Title of the source page. Tabstack auto-fills this from page metadata when left empty.
`favicon`	string	Favicon 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.

company.tsTypeScript

import schema from './company-hiring-velocity.json'

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

tabstack extract json 'https://example.com/pricing' \
  --schema @./company-hiring-velocity.json

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 schemas

Other schemas in this category.

Same category: executive leadership change.
Same category: job posting.
Same category: layoff event.
The job rather than the object: the Extract API.