--- title: "Polymer API" description: "Polymer API: the public per-organization jobs endpoint under api.polymer.co, the Bearer-token Customer API, and how to reach Polymer postings in one call." canonical: https://jobspipe.dev/sources/polymer date_published: 2026-06-16 date_modified: 2026-09-26 author: Dvir Atias --- # Polymer API Polymer documents a public, unauthenticated endpoint under api.polymer.co that returns one organization's published jobs by slug, plus a Bearer-token Customer API in beta for a customer's own jobs and candidates; there is no endpoint enumerating organizations. JobsPipe does not collect Polymer; the same employers' openings reach one search endpoint through the boards JobsPipe does collect, in one record shape across 30+ sources. > Polymer has no public cross-employer jobs API, and JobsPipe does not collect Polymer. This page explains what Polymer exposes and how to reach the same employers through the boards JobsPipe does collect. **Canonical URL:** https://jobspipe.dev/sources/polymer ## Coverage JobsPipe does not collect Polymer. This page explains what Polymer 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 Polymer jobs data is confusing Polymer documents a public, unauthenticated endpoint under api.polymer.co that returns one organization's published jobs by organization slug, plus a Bearer-token Customer API (in beta) for a customer's own jobs, candidates and applications. The public endpoint is rate-limited, and there is no endpoint that enumerates organizations. Polymer careers pages are public per organization at the company's Polymer-hosted job board or its own domain. Slug discovery is the work; the data itself is clean JSON once you have the slug. JobsPipe does not collect Polymer. Employers that run Polymer usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. JobsPipe collects all of those boards, so filter POST /v1/jobs/search by company_name_partial_match_or to reach them. ## Workarounds ### Call the public endpoint per organization Works for slugs you already know. Rate-limited, and no way to list organizations. ### Use the authenticated Customer API Reads one customer's own data with an admin-minted key. Not a path across employers. ### What JobsPipe offers instead JobsPipe does not collect Polymer. Search the same employers by name across the boards JobsPipe does collect (LinkedIn, Indeed, Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever and Paylocity); sources[0].provider on each record names the board it came from. ## 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 ### How do I find a company's Polymer organization slug? Slug discovery is the hard part, because Polymer has no endpoint that enumerates organizations. You have to start from each company's careers page, on its Polymer-hosted job board or its own domain. Once you have the slug, the public endpoint under api.polymer.co returns that organization's published jobs as clean JSON with no key. ### Does the Polymer jobs endpoint need a key or have rate limits? The public per-organization endpoint under api.polymer.co needs no key and is free to call, but it is rate-limited and Polymer does not publish the limits. It returns one organization per call, so covering many employers means many calls against that unpublished ceiling. ### What is the Polymer Customer API? It is Polymer's authenticated API, currently in beta, used with a Bearer token that a customer admin mints. It reads that customer's own jobs, candidates and applications. It is meant for a company working with its own hiring data, not a path to other employers' postings. ### How do I get Polymer job postings without an API? Read each employer's public Polymer careers page yourself, or search the employer by name on boards that carry the same roles. Employers that run Polymer usually also post to LinkedIn and Indeed, which JobsPipe collects, with each record carrying url, status, ghost_score, discovered_at, last_seen_at and a salary range when the posting states one. ## Does Polymer have an API? Polymer documents a public, unauthenticated endpoint under api.polymer.co that returns one organization's published jobs by organization slug, plus a Bearer-token Customer API (in beta) for a customer's own jobs, candidates and applications. The public endpoint is rate-limited, and there is no endpoint that enumerates organizations. Polymer careers pages are public per organization at the company's Polymer-hosted job board or its own domain. Slug discovery is the work; the data itself is clean JSON once you have the slug. ## What JobsPipe returns for Polymer Nothing under "source_or": ["polymer"]: JobsPipe does not collect Polymer. Employers that run Polymer usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. JobsPipe collects all of those boards, so filter POST /v1/jobs/search by company_name_partial_match_or to reach them. Each record comes back with sources[0].provider, status, ghost_score, discovered_at, last_seen_at, seniority, and min_annual_salary_usd and max_annual_salary_usd when the posting states a range. ## 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/polymer. --- 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