--- title: "ZipRecruiter API" description: "ZipRecruiter API: the Partner API and Publisher program, why neither reads the job index, and how to read the same postings through one jobs API." canonical: https://jobspipe.dev/sources/ziprecruiter date_published: 2026-06-16 date_modified: 2026-09-26 author: Dvir Atias --- # ZipRecruiter API ZipRecruiter offers two partner programs and neither reads the index: the Partner API posts an ATS's jobs to ZipRecruiter and returns applicants, and the Publisher program is an affiliate feed for approved job sites. JobsPipe does not collect ZipRecruiter; the same employers' openings reach one search endpoint through the boards JobsPipe does collect, in one record shape across 30+ sources. > ZipRecruiter's APIs are partner-only and built for sending jobs and applicants to ZipRecruiter. JobsPipe does not collect ZipRecruiter. Here is what each program gives you and how to reach the same employers' postings. **Canonical URL:** https://jobspipe.dev/sources/ziprecruiter ## Coverage JobsPipe does not collect ZipRecruiter. This page explains what ZipRecruiter exposes publicly and how to reach the same postings where they are also published on a board JobsPipe does collect (Workday, Greenhouse, Lever, Ashby, LinkedIn, Indeed, SmartRecruiters, Workable, Personio, Recruitee, Teamtailor, EURES, Paylocity, Breezy HR, CV-Library, Y Combinator, Bayt, JobTech (Sweden), Resume-Library, Arbeitnow, Himalayas, Rise, Manatal, Pinpoint, JobScore, HireHive, The Muse, Remotive, Remote OK, Jobicy, Working Nomads, Landing.jobs). ## Why ZipRecruiter jobs data is confusing ZipRecruiter has two API surfaces and neither is a public read API. The Partner API is for ATS vendors, HRIS platforms and staffing firms that push jobs and pull applicants; you need a partnership agreement to get credentials. The Publisher program is an affiliate arrangement: approved publishers receive a search API or feed, show ZipRecruiter listings with tracked apply links, and earn revenue share on applications. Neither program is meant for reading ZipRecruiter's index into your own product. JobsPipe does not collect ZipRecruiter. ZipRecruiter's listings are largely aggregated and syndicated from employer ATSs and other boards, and JobsPipe collects those upstream boards (Workday, Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Paylocity) and the LinkedIn, Indeed and Y Combinator job boards. ## Workarounds ### Apply to the ZipRecruiter Partner API Reserved for ATS vendors, HRIS platforms and large staffing firms that send jobs to ZipRecruiter. Indie aggregators are not in scope, and the API is about your own jobs and applicants. ### Join the Publisher program Fits affiliate job sites: you get a keyed search endpoint or feed, must display listings with ZipRecruiter's tracked apply links, and are paid per application. A revenue-share display deal, not a data license. ### What JobsPipe offers instead JobsPipe does not collect ZipRecruiter. Search the same employers by name across the boards JobsPipe does collect; the employer's own ATS row or its LinkedIn and Indeed rows carry the same posting with a direct apply URL. ## Fields available on every record - `id` - `job_title` - `company` - `company_domain` - `url` - `date_posted` - `discovered_at` - `last_seen_at` - `verified_at` - `status` - `closed_at` - `closed_reason` - `ghost_score` - `seniority` - `cities` - `state_code` - `min_annual_salary_usd` - `max_annual_salary_usd` - `technology_slugs` - `keyword_slugs` - `esco_skills` - `sources` ## FAQ ### Where do ZipRecruiter job listings come from? Mostly from somewhere else first. ZipRecruiter's listings are largely aggregated and syndicated from employer ATSs and other boards. JobsPipe collects those upstream sources, including Workday, Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Paylocity and the LinkedIn and Indeed job boards, so the same posting can usually be found there with a direct apply URL instead of a tracked redirect. ### Can I show ZipRecruiter jobs on my own job site? Only through the Publisher program. Approved publishers get a keyed search endpoint or an XML feed, must display listings with ZipRecruiter's tracked apply links, and earn revenue share on completed applications. Applicants are reviewed for traffic and content quality, and the result is a revenue-share display deal rather than a data license you can use in your own product. ### Can I get ZipRecruiter salary data through an API? Not through any public API. ZipRecruiter shows estimated pay on listings and publishes salary pages, but neither is available programmatically outside its partner programs. JobsPipe returns min_annual_salary_usd and max_annual_salary_usd only when the posting itself states a range, and does not estimate pay, so the numbers you get are the employer's own stated range. ### Can I submit applications to ZipRecruiter jobs programmatically? Not as an outside developer. Applying on behalf of a candidate exists only inside ZipRecruiter's partner and publisher programs, where applicant delivery and tracked apply links are part of the agreement. JobsPipe is read-only: every record carries the posting's url, and for rows from an employer's ATS that url is the employer's own apply page. ## Does ZipRecruiter have an API? Yes, two partner programs, and neither reads the index. The Partner API is for ATS vendors, HRIS platforms and staffing firms: it posts a partner's jobs to ZipRecruiter, receives applicants back, and manages sponsorship, under a partnership agreement. The Publisher program is an affiliate deal for job sites: approved publishers get a keyed search endpoint or an XML feed, must display listings with ZipRecruiter's tracked apply links, and earn revenue share on completed applications. Both programs review applicants and both exist to move traffic and applicants toward ZipRecruiter. JobsPipe does not collect ZipRecruiter; it collects the employer ATSs and boards ZipRecruiter itself aggregates from. ## Is the ZipRecruiter API free? Partners are not charged, but nothing is self-serve. The Partner API comes with a contract aimed at platforms that send jobs to ZipRecruiter. The Publisher program inverts the money: ZipRecruiter pays the publisher per application, and in return controls how listings are displayed and where the apply link goes. Neither is a data license you can buy. JobsPipe's free tier returns 1,000 jobs to start across the boards it collects and the sandbox at POST /v1/sandbox/jobs/search needs no key, but neither returns ZipRecruiter rows. ## How do I get a ZipRecruiter API key? Through one of the two programs. Platforms apply to ZipRecruiter's partnerships team, describe the integration (job posting, applicant delivery, sponsorship), sign a partner agreement and receive Partner API credentials. Job sites apply to the Publisher program, are reviewed for traffic and content quality, agree to the display and tracking requirements, and receive a publisher key for the search API or a feed. No path issues a key to read postings into a sourcing tool, an AI recruiter or a compensation product. For that, create a JobsPipe key and query POST /v1/jobs/search with company_name_partial_match_or. ## What does the ZipRecruiter API documentation cover? ZipRecruiter's partner documentation, shared with approved partners, covers the job-posting feed format (title, description, location, company, apply method, sponsorship flags), the applicant-delivery callbacks and payload, the Apply integration for ATS partners, and account and campaign management. The publisher documentation covers the search endpoint's parameters (search terms, location, radius, days back, page), the response fields (name, snippet, city, state, hiring company, posted time, tracked URL), display rules and attribution. Neither set documents a full-index read or a bulk export. JobsPipe's docs at /docs cover the record shape returned for the boards JobsPipe does collect. ## What JobsPipe returns for ZipRecruiter Nothing under "source_or": ["ziprecruiter"]: JobsPipe does not collect ZipRecruiter. What JobsPipe returns is the same employers' postings where they are published upstream: filter POST /v1/jobs/search with company_name_partial_match_or, job_title_or or job_location_or, and each record comes back with sources[0].provider naming the board it came from (indeed, linkedin, or the employer's own ATS), status, ghost_score, discovered_at, last_seen_at, seniority, the posting's direct url, and min_annual_salary_usd and max_annual_salary_usd when the posting states a range. The sample above shows the shape for one such record found on Indeed. ## Related - **Product:** https://jobspipe.dev/jobs-api - **All sources:** https://jobspipe.dev/sources - **Docs:** https://docs.jobspipe.dev - **Sign up (free tier):** https://jobspipe.dev/signup --- Generated from structured data. View the rendered page at https://jobspipe.dev/sources/ziprecruiter. --- Building this integration yourself? The steps above work. The alternative is one API over 30+ sources, already normalized and deduplicated. Try it right now - no key, no signup: ```bash curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search ``` Sample data, exact live schema. For live data get a free key (1,000 jobs to start) at https://jobspipe.dev/signup, then swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header. Full agent index: https://jobspipe.dev/llms.txt?src=md-twin