Product updates

New filters url_domain_or and url_domain_not in Jobs Search endpoint and Company Search endpoint. This filter allows you to get jobs from specific domains: greenhouse.io, workable.com, linkedin.com, etc.

We've added new domain-based filters to both Jobs Search endpoint and Company Search endpoint:

New filters:

• url_domain_or - Find jobs/companies from specific domains
• url_domain_not - Exclude jobs/companies from specific domains

This allows you to target or exclude jobs from specific platforms like greenhouse.io, workable.com, linkedin.com, etc. Perfect for focusing on direct company postings or excluding certain job boards from your results.

We've standardized the error experience across all endpoints. The error object now consistently includes request_id, code, title, and message.

How to send a slack message for every new job found

We've improved error handling in the app. Notifications now show better titles and descriptions so you can understand what went wrong.

You can export all records from already revealed companies. This is useful if you want to export data without consuming credits.

Company searches that before took too long or were just impossible to run just take seconds. This would typically happen when adding job or technology filters to the search. Here are examples of such queries: - Companies using Snowflake, with a high confidence score in the usage of that technology, from the US. Now it completes in less than 5 seconds - Companies hiring data engineers in the US, UK or Canada. Now completes in 3-4 seconds as well

These and other slow queries are now 2-6x faster. These is how long queries would take before and after the improvement:

Previously, when scraping new jobs, we stored direct logo URLs from external sources. These links often broke due to expiration or CORS issues. We've updated our process to copy and host logo images on our own infrastructure. All newly detected companies will now use a permanent URL format: https://media.theirstack.com/company/logo/xxx.
These links are stable and can be used anywhere.

We have revamped our docs to make it easier to discover TheirStack and its features.

• Navigation: Added a new sidebar to the left of the page to help you navigate the docs in a more intuitive way.
• Merge similar pages: We've merged similar pages to avoid duplication and make it easier to learn about new topics.
• New dataset page: We've added a new page to the docs to help you learn about our datasets.

• Cleaned up the header of the search page for jobs and companies. Now the search name is only displayed in the breadcrumb.
• New Webhooks button to view the webhooks associated with the current search. It indicates whether the search has an active webhook or not.

When enabled, the webhook will fire only once for each company. This is helpful for sales workflows where you want to act on the first job posted (e.g., send an email, add to a CRM) without triggering the workflow for every subsequent job from the same company.

• Example: If active, Company A with 5 jobs → 1 event triggered. If deactivated, Company A with 5 jobs → 5 events triggered.
• If you turn this on for an existing webhook, it will prevent duplicate companies from triggering events going forward. However, companies already sent before enabling the setting won't be remembered, so their jobs may still trigger events.

Track individual webhook performance and credit consumption with a detailed breakdown chart. View which webhooks are using the most credits on the usage page.

• Fixed issue where subscription updates created new subscriptions instead of modifying existing ones.
  • Added ability to customize credit allocation when updating your subscription plan. You can select any number of credits you want to be added to your account.

Resolved two issues affecting app users in company search:

• When filtering by technology category (e.g. "CRM Platforms") not showing a column per technology (e.g. "Salesforce", "Hubspot", "Zoho"...).
• When exporting a list of companies filtering by technology category, there was not a column for each technology of the category.
• When changing the technology filter, the table was filtering by the new technology, but a column was still showing the old technology.