Product updates

We've added two new columns to job exports from the Job Search feature. These columns help you filter and analyze jobs more effectively when exporting your results.

The new columns are:

• employment_status - Displays the employment statuses for the job. This can include values like "Full-time", "Part-time", "Contract", or "Temporary". When a job has multiple statuses, they're listed as a comma-separated string.

• seniority - Indicates the seniority level of the position. This field uses values like c_level, staff, senior, mid_level, or junior to help you categorize roles by experience level.

These columns are automatically included in all job exports (CSV and Excel formats), so you'll have richer data to work with when analyzing job postings or building integrations.

We've added rate limit information to API response headers, making it easier to monitor your usage and manage your API integrations.

Every API response now includes these headers:

• RateLimit - Current quota status per policy with remaining requests and reset time
• RateLimit-Policy - Applied policy definitions with limits and window durations
• RateLimit-Remaining - Shows how many requests you have left in each time window
• RateLimit-Reset - Tells you when each limit resets (in seconds)
• RateLimit-Limit - Your total allowed requests per window

For complete details on which headers are included, what they mean, and how to use them, check out our API documentation. The rate limiting section explains everything you need to know about rate limits and how to handle them in your applications.

We've added 48 new technologies to our detection system, expanding coverage across artificial intelligence, data science, supply chain management, tag management, and enterprise software categories.

Artificial Intelligence & Machine Learning

• IFS.ai
• NVIDIA Nemotron
• NVIDIA Dynamo
• RAPIDS
• NVIDIA BioNeMo
• Triton
• Gurobi Optimizer
• NVIDIA PhysicsNeMo

Data Science & Analytics

• Google OR-Tools
• Waaila
• UTM.io
• HiGHS
• PyVRP

Supply Chain & Logistics

• Customer Order and Network Density OptimizeR (CONDOR)
• RouteSmart Technologies
• Hexaly
• NextBillion.ai
• UPS

Tag Management & Data Quality

• Website Observer
• Enterprise Tag Manager
• DataTrue
• Tag Inspector
• TAGLAB
• Code Cube
• Tag Insight
• Data Kojak
• Netvigie Tracking
• Verified Data

Application Development & Infrastructure

• Nextmv
• FlashInfer
• Strimzi Kafka Operator
• SGLang

Enterprise Software

• Maximo Asset Management
• SAP Field Service Management
• Apache KIE
• NEC

Mapping & Location Services

• GraphHopper Directions API

Other Categories

• Solvice - Resource Scheduling
• Accutics - Marketing Performance Management
• LMCache - Content Delivery Network
• Leaf Signal - Conversion Optimization
• Avo - Data Management Platform
• Adobe Experience Platform Assurance - Application Testing
• Terminus - Link Management Tools
• LlamaIndex - Document Management
• Data On Duty - GDPR Compliance
• Raisely - Fundraising and Donation Management
• Jarvi - Recruitment

We're excited to announce that TheirStack Jobs Data is now available as an integration in Clay, giving you access to real-time job posting data directly within your GTM workflows.

How to Use

To get started with the TheirStack integration in Clay:

1. Go to Clay and create a new table.
2. Go to "Add Enrichment" in your Clay table
3. Select "TheirStack" from the integrations list
4. Choose "Get Company Jobs" to retrieve job postings

For more information about our job data, check out our Job Search API documentation. You can also learn more about the integration on Clay's TheirStack integration page or read about it in Clay's product roundup changelog.

We've updated our free plan with clearer limits while keeping it completely free forever.

Every month, free plan users get 50 company credits and 200 API credits. New limits include:

• Browse up to 5 pages of search results
• View up to 25 results per page
• Rate limit of 2 requests per second

For complete details on all features and limits, see our pricing plans page. Need more? Upgrade to any paid plan for unlimited pages, up to 500 results per page, and 4 requests per second at your billing settings.

We've made several improvements to our platform over the past few weeks to boost stability and performance. Here's what's gotten faster:

Webhooks

Webhooks are now more reliable and faster than ever. We've separated webhooks into different pipelines to eliminate bottlenecks and keep things running smoothly.

Job Searches

When you filter job searches by company identifiers (domain, LinkedIn URL, or name), you'll notice significant speed improvements:

• Searches for companies that don't exist in our database are now 3x faster than before
• Searches for companies that do exist in our database are now 2x faster than before

Technographics

Technographics queries are now 2x faster, giving you the technology insights you need in half the time.

Company Searches

Filtering company searches by technology is now 25% faster, making it quicker to find companies using specific tech stacks.

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. This change helps us maintain our low pricing while keeping the platform sustainable for everyone.

Read more about this update in our blog post.

The seniority field in every job object in the Job Search endpoint can take one of these 5 values: c_level, staff, senior, mid_level, junior

Previously, seniority was not being correctly assigned for certain job titles:

• All “Vice President” roles were sometimes misclassified, being considered as mid-level roles, and all "VP" roles were considered C-Level.
• The “Staff” seniority label was applied too broadly, including roles like “Staff Nurse” or “Staff Physician” that do not represent Staff-level IC (Individual Contributor) positions.

With this update, seniority assignment has been improved:

• All “Vice President” roles are now consistently marked as Senior, rather than C-Level. While VP might sound like a C-Level title, in many organizations—especially banks and financial institutions—VP is a very common title that better aligns with Senior-level responsibility.
• The “Staff” seniority is now reserved only for explicit Staff-level IC roles, such as “Staff Engineer” or “Member of the Technical Staff.”
• Roles like “Staff Nurse” or “Staff Physician” are no longer misclassified as Staff; instead, they are mapped to more appropriate levels, often mid-level.

We've added a new exclusion filter called job_description_contains_not to the Jobs Search endpoint.

This filter helps you exclude jobs that contain specific words in their descriptions. Here's how it works:

• Whole word matching: It only matches complete words using word boundaries, so searching for "quality" won't exclude jobs mentioning "inequality"
• Smart case handling: Searches are case-insensitive by default, but if you use uppercase patterns, we'll respect the exact casing
• Multiple exclusions: You can exclude jobs containing any of several different words at once

Perfect for filtering out roles you're not interested in, like excluding "internship" positions or "remote" jobs when you prefer in-office work.

Previously, when using the Jobs Search endpoint, you needed to include at least one of these required filters:

• posted_at_max_age_days
• posted_at_gte
• posted_at_lte
• company_name_or

We've expanded the list of required filters to include two new options:

• company_domain_or
• company_linkedin_url_or

Now you can search for jobs from specific companies using their domain or LinkedIn URL, without needing to specify dates or company names. This gives you more flexibility when targeting jobs from particular organizations.

We've just released our new locations catalog endpoint, making it simple to find and search through location data when you need precise geographic targeting.

This is especially useful when you're integrating our API into your application and want to use location-based filtering:

1. A user searches for "Paris" in your app
2. Your system calls GET /v0/catalog/locations?name=Paris to get Paris's location ID
3. You use that ID with our Jobs endpoint using "job_location_or": [{"id": "XXX"}] to return jobs only in Paris

The workflow is straightforward and keeps the complexity hidden from your users.

🚧 Beta Feature: This new filtering capability is currently available for recent jobs (posted within the last 3 months ±). We're actively expanding coverage to older jobs and improving the system based on user feedback. 🚧

We've introduced new location filters job_location_or and job_location_not to the Jobs Search endpoint and Company Search endpoint for precise geographic targeting in job searches.

These new filters address several limitations of the existing location_pattern_or filter:

• Greater precision - Target specific cities, states, or regions with exact accuracy. When searching for San Francisco, results will be limited to California, U.S., and won't include other cities with the same name elsewhere in the world
• Hierarchical location searches - Search for "Europe", "China" or "California" and get all jobs within that region. The hierarchical location data enables searches at any level (country, state, province, city, etc.). This wasn't possible with the previous text-based approach, which couldn't understand location hierarchies
• Multi-language location searches - Search for locations in different languages using the same location IDs, ensuring consistent results regardless of the search language. With the previous string matching approach, searching for "Germany" wouldn't match all occurrences since "Deutschland" could be used instead
• Cross-country city searches - Search across multiple cities in different countries simultaneously. This supports state/city queries across countries (e.g., Alabama, US and London, UK) in a single search request
• Improved flexibility - Easily combine multiple location criteria or exclude specific areas
• Better performance - More efficient searches using indexed location data
• Structured data - Uses normalized location IDs instead of text pattern matching

You can use the locations catalog endpoint to search for the IDs of your desired locations.