How to Choose the Best Way to Access TheirStack Data
Guidance to help you choose the most suitable way to access TheirStack data (App, API, Webhooks, or Datasets) for your use case, scale, and freshness needs—without prescribing a single path.
TL;DR
- If you're not a developer, use the App.
- If you need more than 1M records / month, use Datasets.
- If you want to get notified when (1) new jobs are posted or (2) new companies start using a new technology, use Webhooks.
- If you want to enrich an external system on demand, use the API.
Basics
- Same data for all methods: Every delivery method accesses the same underlying dataset and quality.
- Filtering: All filters are available in the App, API, and Webhooks. Datasets are exported as flat files (CSV/Parquet) without server-side filtering.
Delivery methods
App (UI)
Use the App when you want to explore, iterate, and export data without writing code.
-
What it’s best for
- Validating data quality and fields quickly
- Running ad-hoc searches and refining filters interactively
- Exporting results to CSV/Excel or sending to external tools
-
Pricing
- Uses company credits
API (on-demand)
Use the API when you need programmatic, on-demand access for enrichment or user-triggered actions.
- What it’s best for
- Enriching CRM or product records when a user opens a page or clicks a button
- Server-to-server lookups inside workflows (e.g., scoring, validation)
- Synchronous product features that fetch data on demand
- Pricing
- Consumes API credits; pay per record returned
- When not to use
- If you’re polling or batching requests on a schedule, prefer Webhooks for push delivery, retries, and lower operational overhead
- Learn more
Webhooks (real-time)
Use Webhooks when you need to ingest fresh data continuously without polling.
- What it’s best for
- Keeping an internal database or pipeline in sync
- Triggering workflows in tools like Zapier, Make, n8n, or your services
- Event-driven integrations based on saved searches
- Pricing
- Consumes API credits; pay per record returned
- Learn more
Datasets (bulk + historical)
Use Datasets when you need large-scale access for warehouses, analytics, or ML.
- What it’s best for
- Loading into a data warehouse or data lake (S3, BigQuery, Snowflake, etc.)
- Historical analysis and model training
- High-volume consumption (>1M records/month)
- Pricing
- Flat subscription; more cost‑efficient above ~1M records/month
- Learn more
- Overview: Datasets
- Jobs schema and coverage: Job data
- Access steps: Obtaining access to your datasets
Examples
- Sales or RevOps team wants to test a new ICP and export a CSV for outreach → App (UI)
- Product team needs new US tech jobs streamed into an internal DB every hour → Webhooks
- Data team wants multi-year job postings for trend analysis and modeling → Datasets
How is this guide?
Last updated on
How to Check if a Technology or Keyword Is Available
Learn how to find out whether TheirStack tracks a specific technology or buying intent keyword, download the full catalogs, use job description search as a workaround, and request new keywords through the Support Center.
How to create a niche job newsletter with TheirStack MCP
Learn how to create a weekly curated job newsletter using Claude.ai and TheirStack MCP. Automate job newsletter creation with a reusable template — no code needed.