Frequently Asked Questions
General Questions
In this section, we've collected answers to general questions about job posting data and Techmap. Learn more about the importance of job postings, where our data comes from, and the scope of our offerings.
About Job Postings
- Why do I need job postings?
- Job postings provide valuable insights into the hiring activities, recruitment strategy, and technology usage of businesses, as well as the job market in general. Common uses include labor market research, competitive intelligence, sales lead generation, job board enrichment, and AI model training.
- What is job posting data?
- Job postings, also known as job ads or job listings, are advertisements created by employers to attract candidates for open positions. Job posting data is the structured information extracted from these ads - typically including job title, location, description, qualifications, employment type, company name, and source portal.
- Where does the data come from?
- Data is collected by continuously crawling publicly available sources: company ATS career pages, job boards, job aggregators, and employment offices. Each page is parsed into a standardized JSON structure, normalized, and enriched before storage. The full list of 185 covered source portals is in the portal explorer.
- How far back does your data go?
- Job postings from January 2020 onwards are available as historical datasets via AWS Data Exchange. The API and current data feeds contain the last 3 months only. Per-country monthly volumes since 2020 can be explored in the data explorer.
About Techmap
- What do you offer?
- Techmap provides job posting data in three forms: a Job Posting API (last 3 months, all countries, billed per request via RapidAPI), job data feeds on AWS Data Exchange (per-country subscriptions, files updated hourly), and historical datasets from January 2020 onwards. Typical customers include data scientists, software developers, and product managers building labor market tools, job boards, or sales intelligence platforms.
- What is the difference between the Jobs API, RSS API, data feeds and historical datasets?
- Jobs API: search the last 3 months of job postings in all countries with filters; returns JSON, 10 postings per request, $1 per 1,000 job postings via RapidAPI.
- RSS API: the same postings as RSS/XML feeds, e.g. for job board backfill; also billed per request via RapidAPI.
- Data feeds: all postings of a country as daily gzip-compressed JSON Lines files on AWS S3 via AWS Data Exchange, refreshed hourly, rolling 3-month window; $400 per country & month.
- Historical datasets: every daily file of a country since January 2020, same format; $2,400 - $4,800 per country, one-time.
- What types of job postings do you offer?
- The database includes full-time, part-time, remote, hybrid, and on-site positions across all industries, contract types, career levels, and company sizes. Work arrangement (remote/hybrid/on-site) is available as the structured
workPlacefield when stated in the original posting.
- Which countries do you cover?
- 250 countries and territories are covered (incl. world-wide remote jobs). Over 100 countries have more than 1K new job postings per month, and 20+ have more than 100K. Current per-country volumes are in the country explorer.
- Why do you say 250 countries and territories?
- Geographic coverage follows the ISO 3166-1 standard (249 two-letter codes covering 193 sovereign nations and 56 dependent territories). One additional code covers fully remote positions with no fixed location, bringing the total to 250. All country filters in the API and data feeds use standard ISO 3166-1 alpha-2 codes (e.g. us, de, fr, or ## for remote (URL encoded:
%23%23)).
About Source Coverage
- Is Indeed included?
- No. Indeed job postings are not included. The data comes from 185 other sources: ATS career pages (e.g. Greenhouse, Lever, Workday, SAP SuccessFactors, iCIMS), job boards, aggregators and public employment offices. The full list is in the portal explorer.
- Is LinkedIn included?
- Yes. LinkedIn job postings are included. For coverage details and monthly volumes, see the LinkedIn portal page.
- Is a specific (local) job board included? Can I see your source list?
- Yes, the complete source list is public: the portal explorer lists all 185 sources - 120 ATS platforms, job boards, aggregators and 7 public employment offices - with monthly volumes per source. The country explorer shows which sources are active in each country. If a board is not listed, it is not included.
- Which ATS platforms are covered?
- We cover 120 ATS career page platforms. Coverage varies by region - some platforms focus on the US while others are stronger in Europe. The full list with monthly job volumes per portal is in the portal explorer.
- Which countries have the best coverage?
- Coverage is strongest for the US, UK, Germany, France, and other large markets. Over 100 countries have more than 1000 new job postings per month, and 20+ have more than 100K. Current per-country monthly volumes are listed at country explorer.
- Can you scrape a specific source on request?
- No. Only pre-existing datasets and data feeds from sources already in the pipeline are available for purchase. Custom or one-time scraping of new sources is not offered. However, if you have a larger source contact us - we might be interested to add it to our sources.
Technical Questions
Here we cover technical questions related to Datafeeds, Datasets, and the Data API, as well as questions about data updates, quality, and usage.
About Datafeeds & Datasets
- What is a datafeed?
- A datafeed is a daily export of job postings per country, delivered as gzip-compressed JSON Lines files (.jsonl.gz) on AWS S3 via AWS Data Exchange. Each line contains one complete job posting in JSON format. Files range from a few kilobytes (small countries) to over 100 MB compressed - and up to several gigabytes uncompressed - for high-volume markets. Subscribers typically copy files to their own S3 bucket for further processing.
- What is a historical dataset?
- A historical dataset contains all daily data files for a specific country from January 2020 to the present, delivered as gzip-compressed JSON Lines files on AWS Data Exchange. It is a one-time purchase (not a recurring subscription). Historical datasets are the only way to access data older than 3 months.
- What data formats are supported?
- Data files are delivered exclusively as gzip-compressed JSON Lines (JSONL). The API also returns JSON. Other formats (CSV, XML, Parquet, RSS, Atom) are not natively available, but we can provide sample conversion code. Contact our Data Team for help.
- How large are the daily data files?
- File sizes vary significantly by country: from a few kilobytes for small markets to over 100 MB compressed (gzip) for high-volume countries such as the US or UK. Uncompressed, the same files can require up to several gigabytes. The number of job postings per file depends on the age of the file - postings typically remain active for several weeks to 3 months.
- How are duplicate job postings handled?
- A duplicate is defined as a job posting with the same company name, city, country, and job title appearing within a 3-day window. Duplicates are kept in the dataset but flagged with the field
isDuplicate: true. The fieldisDuplicateOfcontains the ID of the earliest identical posting. This applies across portals - the same job appearing on a job board and a company career page is marked as a duplicate rather than removed. Kept duplicates are useful for analysis, e.g. where a company distributes its job ads and how much it spends on them.
- Are active and expired jobs marked?
- Partly. Postings are not re-checked for removal after collection. Each posting has a
dateActivefield - the assumed expiry date, taken from the posting's schema.orgvalidThroughor set todateCreated+ 30 days - anddateExpiredwhen the posting states it. In the API,isActive=truereturns only postings whosedateActivelies in the future. Postings leave the API and data feeds after about 3 months.
- Is there data before 2020?
- No. The archive starts in January 2020. Historical datasets contain every daily file of a country from January 2020 to today.
- Do job postings include contact details?
- Only when the original posting states them. The
contact.*fields (name, email, phone, address) are filled for about 31% of postings in the data feed and dataset files. Techmap does not add or enrich contact data of hiring managers.
- How many jobs do you have for a country, job title or company?
- Monthly volumes per country are in the country explorer and per source in the portal explorer. For a specific job title or company, query the free BASIC plan of the Jobs API with the
titleorcompanyfilter (last 3 months), or ask our Data Team.
- How many job postings will I receive?
- There is no limit on the number of job postings per country - you receive everything collected. Volume varies by country: approximately 1 million new job postings per month for the USA. Current per-country monthly volumes are in the country explorer.
About the Data API
- What can I do with the API?
- The Job Posting API provides programmatic access to job postings from the last 3 months. Filter by
countryCode,portal,timezone,dateCreated,hasSalary,workPlace, city, and more. Common uses include job search tools, analytics pipelines, and labor market dashboards.
- How many job postings does one API request return?
- Each API request returns 10 job postings. To retrieve more results, paginate using the
pageparameter. A plan with 3000 requests per month therefore provides access to up to 30000 job postings - not 3000.
- What is the difference between requests and job postings in the pricing?
- The API is metered by requests. Each request returns 10 job postings. 100 requests = 1000 job postings = $1. A plan listed as '3000 requests' provides up to 30000 job postings per month. See the RapidAPI pricing page for current plan details.
- How far back can I query with the API?
- The API contains only the last 3 months of job postings. The
dateCreatedfilter accepts any date within that window. Job postings older than 3 months are removed from the API. For data from January 2020 onwards, use the AWS Data Exchange historical datasets.
- Does the API provide historical job data?
- No. The API contains only the last 3 months of job postings. Historical data from January 2020 onwards is available exclusively via AWS Data Exchange as daily compressed JSON Lines files.
- How is the API billed?
- The API is billed per request via RapidAPI at $1 per 100 requests (1000 job postings). A free BASIC plan is available with 100 requests (1000 job postings) per month. For overage cost and current plan options & limits, see the RapidAPI pricing page.
- What data format does the API return?
- The API returns JSON. Query parameters are passed as URL parameters. Each response includes a results array with up to 10 job postings and pagination metadata. A complete field reference is in the Job API Data Dictionary.
- How can I access the API?
- Go to the API page on RapidAPI, create an account, and subscribe to a plan. Use the API key from RapidAPI in the
Authorization: Bearerheader. Full documentation is on RapidAPI and in the API overview.
About Data Updates & Quality
- How quickly does a new job appear after it goes live?
- Scrapers run at least twice per day per source, filling the API directly on each run. S3 data files are refreshed hourly. A new job posting typically appears in the API within hours of collection, and in the S3 files within the next hourly export cycle.
- How often is each source crawled?
- Every source is scraped at least twice per day. New job postings fill the API directly as they are collected. Daily data files on AWS S3 are exported and updated hourly, and stabilize approximately 2 days after the target date to ensure all pipeline data is included.
- What fields does each job posting contain?
- Each posting includes: job title, full description (as HTML and plain text), company name and logo, location (address, city, country, zip), employment type, work arrangement (
workPlace: remote/hybrid/on-site when available), salary (amount, currency, period when available), skills and tags, source portal, and creation/scraping dates. The full field list is in the Job API Data Dictionary and job data overview.
- Is salary data included?
- Yes, when salary or compensation information is present in the original job posting, it is extracted and stored in structured salary fields (amount, currency, period). If a posting does not mention salary, those fields are empty.
- Is remote/hybrid/on-site work arrangement included?
- Yes. When the work arrangement is stated in the original posting, it is stored in the structured
workPlacefield. If the posting does not specify a work arrangement, the field is empty.
- Are company firmographics included (size, funding, HQ)?
- No precomputed firmographics are included. The
orgCompanysub-document contains whatever is stated on the job posting page: company name, logo, website, and tags when available. Data such as headcount, funding stage, or HQ location must be derived or enriched by the customer from the raw data.
About Data Usage
- How does AWS Data Exchange work, and where is my S3 bucket?
- You subscribe to a data feed or buy a dataset with your AWS account on AWS Data Exchange; AWS bills it with your AWS invoice. After subscribing, AWS Data Exchange grants your account read access to the S3 bucket with the daily files - the bucket alias and key prefix are shown under 'Entitled data' in the AWS Data Exchange console. New files appear there automatically. You can read them directly or copy them to your own S3 bucket with the AWS CLI or SDK. All data is stored in AWS eu-central-1 (Frankfurt, Germany). See the developer section for step-by-step commands.
- How do I process the JSON Lines files?
- Decompress the gzip files and read one line at a time - each line is a complete JSON object. Most languages have native support for this pattern (e.g. Python's
gzip+jsonmodules). See the developer section for code examples.
- Can I get data in XML, CSV or Parquet format, or via webhooks?
- Data files are gzip-compressed JSON Lines, and the Jobs API returns JSON. XML is available as RSS feeds via the RSS API. CSV and Parquet are not delivered natively, but JSON Lines converts easily - we can provide sample conversion code. There are no webhooks: poll the API or RSS API, or pick up new files from the S3 bucket on AWS Data Exchange. Contact our Data Team for help.
- Can I buy only a filtered subset (e.g. an industry, occupation or company)?
- No. Data feeds and datasets always contain all postings of a country; you apply your own filters in your pipeline using fields such as
industry,occupation,companyorportal. For smaller volumes, the Jobs API returns filtered results directly - e.g. by title, company, occupation, industry, skills, country, city, portal, date, salary or work arrangement.
- Can I get only jobs from direct employers, without recruiters and aggregators?
- Yes. In the Jobs API,
isDirect=truereturns only postings linked directly to the hiring company (not via a job board), andisRecruiter=falseexcludes postings from recruiting firms. Both fields (isDirect,isRecruiter) are also in every record of the data feed and dataset files, so you can filter them yourself.
- Can I derive or compute signals from the raw data?
- Yes. Derived insights, categorization, and enrichment with your own AI models are allowed. Precomputed signals (e.g. hiring velocity, company headcount estimates) are not provided by Techmap and must be computed from the raw job posting data by the customer.
Legal and Business Questions
This section addresses some common questions about legal and business issues, and covers topics related to our contracts, pricing, billing, trials, and samples. As a disclaimer, please note that we are not legal professionals and laws vary by country and state.
About Subscriptions
- How can I subscribe to a Job Datafeed?
- Our country feeds are available for direct subscription via AWS Data Exchange. Contact our Data Team with your country requirements if a country is missing or you're interested in a bundle. We can also provide data samples if needed.
- How can I buy historical datasets?
- Our historical datasets are available as a one-time purchase via AWS Data Exchange. Contact our Data Team with the countries and date range you need. Historical data covers January 2020 to present.
- How do I subscribe to the API?
- Subscribe directly on the RapidAPI page. A free BASIC plan with 100 requests (1000 job postings) per month is available that can be upgraded if necessary.
About Billing, Pricing and Payments
- What are your pricing plans?
- The API is billed at $1 per 100 requests (1000 job postings) via RapidAPI. A free BASIC plan with 100 requests (1000 job postings) per month is available. Data feeds and historical datasets on AWS Data Exchange are priced per country - see the pricing page.
- What does a country, a bundle or all countries cost?
- Per country, a data feed costs $400 per country & month (with lower monthly rates for 3- and 12-month terms), and a historical dataset $2,400 - $4,800 per country, one-time depending on the country's volume. The Jobs API covers all countries in every plan at $1 per 1,000 job postings. For bundles of several countries or all countries, ask our Data Team for an individual quote. Current prices are on the pricing page.
- Can I pay by invoice or bank transfer?
- Data feeds and historical datasets are billed by AWS through your AWS account - whether you pay the AWS invoice by bank transfer or card depends on the payment method set in your AWS account. API plans are paid via RapidAPI by credit card. Techmap does not invoice directly.
- Do you offer discounts?
- Two discount programs are available for data feeds on AWS Data Exchange (not the API):
- Startup discount (50%): For companies under 5 years old, valid for up to 12 months.
- Research / academic discount: Requires proof of affiliation - a letter from your advisor or a document showing a university email address associated with the project.
About Trials and Samples
- Is there a free API trial?
- Yes. The BASIC plan of the Jobs API on RapidAPI is free and includes 100 requests (1,000 job postings) per month. The RSS API also has a free BASIC plan with 30 requests (300 job postings) per month. The free API key works for every country, so you can test any country right away.
- Do you offer sample data files for feeds?
- Yes. The Luxembourg job data feed on AWS Data Exchange is free - subscribe to it for full data feed access in the same format as every paid country feed. For samples from other countries, contact our Data Team.
- Are sample datasets available for download?
- Yes. The Luxembourg historical dataset on AWS Data Exchange is free and contains all postings since January 2020. Some datasets are also available on Kaggle - see the data overview page for download links. For a specific country sample, contact our Data Team.
About Data Privacy & Legitimacy
- Is the job posting data GDPR compliant?
- Yes. Techmap GmbH is based in Germany, and all data is stored in AWS eu-central-1 (Frankfurt). Job postings have a business context and contain no personal data on private individuals. If you operate a job board and receive personal data from applicants, you must apply your own GDPR compliance measures for that applicant data.
- Is it legal to use scraped job postings?
- Yes. Crawling and processing publicly available job postings is legal. We collect data in compliance with applicable laws and regulations. For jurisdiction-specific legal questions, consult a legal professional.
- May I display the jobs on my job board or app, store them, or resell them?
- You may store job postings in your own database for internal processing, AI enrichment, candidate matching, analytics, and public display on job portals. Deriving signals, categorizations, and enrichments with your own AI models is allowed. You may not resell the raw job postings to third parties. AWS Data Exchange subscriptions are governed by the AWS Data Subscription Agreement for AWS Marketplace.
If you have any additional questions about Techmap's job data,
please don't hesitate to contact us. We're here to help!