Schema library travel

Return an attraction or experience listing from a public page.

Pass this JSON Schema and a public source URL to/extract/json. Structure public location, description, hours, price, and booking context shown on the source.

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 attraction or experience listing.

Tourist attraction or bookable travel experience listing from an OTA or attraction platform.

Field	Type	What it holds
`name`	string, required	Name of the attraction or experience.
`attraction_type`	string, required	Category of the attraction or experience.
`operator_name`	string	Name of the operator or organizer.
`address`	string	Meeting point or address.
`city`	string, required	City where the experience takes place.
`country`	string, required	Country where the experience takes place.
`latitude`	number	Latitude of the meeting point or main location.
`longitude`	number	Longitude of the meeting point or main location.
`description`	string	Full description of the experience.
`duration_minutes`	number	Duration of the experience in minutes.
`min_participants`	number	Minimum number of participants.
`max_participants`	number	Maximum number of participants.
`age_minimum`	number	Minimum age requirement.
`price_adult_usd`	number	Adult price in USD.
`price_child_usd`	number	Child price in USD.
`price_currency`	string	Currency code for the prices.
`booking_required`	boolean	Whether advance booking is required.
`cancellation_policy`	string	Cancellation policy description.
`languages_offered`	array	Languages in which the experience is offered.
`inclusions`	array	What is included in the experience.
`exclusions`	array	What is not included in the experience.
`review_rating`	number	Average review rating.
`review_count`	number	Total number of reviews.
`images`	array	URLs of experience images.
`category_tags`	array	Category tags or labels.
`booking_url`	string	URL to book the experience.
`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.

attraction.tsTypeScript

import schema from './attraction-experience.json'

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

tabstack extract json 'https://example.com/pricing' \
  --schema @./attraction-experience.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: flight price snapshot.
Same category: hotel listing.
Same category: restaurant listing.
The job rather than the object: the Extract API.