Schema library b2b-intel
Return a funding-round record from a public page.
Pass this JSON Schema and a public source URL to/extract/json. Capture public funding announcement details with source context and dates.
TEXT
MARKDOWN
LINKS
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 funding-round record.
Schema for venture capital and private equity funding round records.
| Field | Type | What it holds |
|---|---|---|
company_name | string, required | Name of the company that raised funding. |
company_domain | string | Website domain of the funded company. |
round_type | string, required | Type of funding round. |
amount_usd | number | Amount raised in this round in USD. |
currency | string | ISO 4217 currency code of the raise. |
announced_date | string, required | Date the funding round was publicly announced. |
closed_date | string | Date the funding round officially closed. |
lead_investor | string | Name of the lead investor. |
co_investors | array | List of participating co-investors. |
total_raised_usd | number | Total funding raised to date in USD. |
post_money_valuation_usd | number | Post-money valuation in USD. |
pre_money_valuation_usd | number | Pre-money valuation in USD. |
investor_count | number | Total number of investors participating in this round. |
use_of_funds | string | Stated intended use of the raised funds. |
company_hq_city | string | City of the company's headquarters. |
company_hq_country | string | Country of the company's headquarters. |
company_industry | string | Industry of the funded company. |
source_type | string | Type of source (e.g., press_release, crunchbase, news_article). |
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.
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.
import schema from './funding-round.json'
const res = await client.extract.json({
url: 'https://example.com/pricing',
json_schema: schema,
})tabstack extract json 'https://example.com/pricing' \
--schema @./funding-round.jsonAdaptation
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.
- Same category: api documentation endpoint.
- Same category: company profile.
- Same category: competitor profile.
- The job rather than the object: the Extract API.