Quick Summary
Starting October 9, 2025, blur_company_data won't have any effect when filtering by a single company and will be charged as if it wasn't there. If jobs are returned, you'll be charged 1 API credit per job. If no jobs are returned, you'll be charged 0 API credits. This change helps us maintain our low pricing while keeping the platform sustainable for everyone.
What's Preview Mode?
Our Job Search and Company Search endpoints include a preview mode that returns the same data with some fields blurred (blur_company_data = true). This feature is perfect for sales software that needs to show data previews to users without consuming credits.
Want to learn more? Check out our preview mode documentation.
Why We're Making This Change
We're committed to keeping our prices as low as possible. Four months ago, we reduced job costs by up to 3x, and we want to keep lowering costs as we grow.
However, we've noticed some users are using blur_company_data in ways we didn't originally intend. When you filter by a single company identifier, the blurring doesn't really work since you already know which company you're targeting.
Some users have been using this combination to:
- Check if a company posted jobs in specific date ranges: how many jobs has Apple posted in the last 30 days?
- See if a company has jobs with certain titles: how many sales positions has Anthropic opened in the last quarter?
- Discover a company's technology stack: Is Lovable using Snowflake?
While we understand the appeal, providing this level of detailed company intelligence for free isn't sustainable for our business.
What's Changing?
Effective October 9, 2025, the blur_company_data parameter will no longer provide free previews when used in conjunction with single company filters. Queries using both blur_company_data = true and any single company identifier (company_domain_or, company_linkedin_url_or, company_name_or, company_linkedin_url_or, company_id_or, company_name_partial_match_or) will consume credits for returned job data as the blur_company_data wasn't present.
We know this might feel unexpected, and we completely understand you've been using features as they were available. These changes help us keep the platform sustainable for all our users while maintaining our commitment to affordable pricing.
How to minimize API cost?
If you're looking to do a count (Eg: 'how many jobs has Apple posted in the last 30 days?', 'How many sales positions has Anthropic opened in the last quarter?'), the best is to set limit to 1. If we have jobs, this will cost you 1 API credit. If we don't, this will cost you 0 credits.
Thanks for your understanding as we work to keep TheirStack valuable for everyone!