This API provides access to job postings that have been crawled and scraped directly from various sources up to 3 months in the past.

The job postings are sourced directly through web crawling and scraping from a diverse range of platforms, including:

• Techmap's Web Crawlers
• ATS Career Pages (e.g., Workday, Personio, JazzHR, ...)
• Job Boards (e.g., LinkedIn, Monster, Dice, ...)
• Job Aggregators (e.g., Indeed, Glassdoor, Xing, ...)
• Employment Offices (e.g., German Arbeitsagentur, ...)

With this API, you can seamlessly integrate job postings from multiple sources into your applications, enabling backfilling of job boards, detailed analysis, company monitoring, or automated job agents.

Boolean Queries

Most query parameters in the API support flexible Boolean queries, enabling precise filtering of job postings using multiple keywords, keyphrases, and logical operators. Below are the supported query types:

• Should Searches (OR): Keywords separated by a comma will match at least one keyword. Example: ?title=java,developer Matches jobs with either "java" or "developer" in the title.

• Must Searches (AND): Keywords with an encoded + sign (%2B in the URL) must be present. Example: ?title=%2bjava,%2bdeveloper Matches jobs with both "java" and "developer" in the title.

• Must-Not Searches (NOT): Keywords with a - sign before are excluded. Example: ?title=%2bjava,-mysql Matches jobs with "java" but not "mysql" in the title.

• Keyphrase Searches: Words separated with spaces in double quotes count as one keyword / keyphrase. Example: ?city="New York" Matches jobs in "New York".

Notes

• Parameter Combinations: You can combine most parameters, but some combinations may not work together. For example, a geo bounding box cannot be used together with a geo distance search.
• Field Availability: Not all fields are populated for every job posting. Commonly missing fields include state, postCode, or department.
• Authentication: Every request needs your marketplace key - see How to authenticate below.

Examples

• Jobs in Germany:

  curl -X GET "https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/count?countryCode=de" -H "X-RapidAPI-Key: YOUR_API_KEY" -H "X-RapidAPI-Host: daily-international-job-postings.p.rapidapi.com"
  

• Remote jobs in core US Timezones (UTC-8 to UTC-5):

  curl -X GET "https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/count?workPlace=remote&timezoneMin=-8&timezoneMax=-5" -H "X-RapidAPI-Key: YOUR_API_KEY" -H "X-RapidAPI-Host: daily-international-job-postings.p.rapidapi.com"
  

• Jobs in southern Netherlands below latitude 52.25:

  curl -X GET "https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/count?countryCode=nl&geoTopLeftLat=52.25&geoTopLeftLng=0&geoBottomRightLat=32.25&geoBottomRightLng=10" -H "X-RapidAPI-Key: YOUR_API_KEY" -H "X-RapidAPI-Host: daily-international-job-postings.p.rapidapi.com"
  

• Jobs in the Healthcare industry in the UK:

  curl -X GET "https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/count?countryCode=uk&industry=healthcare" -H "X-RapidAPI-Key: YOUR_API_KEY" -H "X-RapidAPI-Host: daily-international-job-postings.p.rapidapi.com"
  

• Jobs for Java Developers in San Francisco:

  curl -X GET "https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/count?occupation=programmer&geoPointLat=37.757&geoPointLng=-122.449&geoDistance=100mi" -H "X-RapidAPI-Key: YOUR_API_KEY" -H "X-RapidAPI-Host: daily-international-job-postings.p.rapidapi.com"
  

• Jobs for JavaScript Developers in New York, USA:

  curl -X GET "https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/count?skills=JavaScript&countryCode=us&city=%22New%20York%22" -H "X-RapidAPI-Key: YOUR_API_KEY" -H "X-RapidAPI-Host: daily-international-job-postings.p.rapidapi.com"
  

• Jobs in English located in Germany:

  curl -X GET "https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/count?countryCode=de&language=en" -H "X-RapidAPI-Key: YOUR_API_KEY" -H "X-RapidAPI-Host: daily-international-job-postings.p.rapidapi.com"
  

• Remote jobs for Web3 Developers:

  curl -X GET "https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/count?skills=ledger,Blockchain,Web3,ethereum,ether,bitcoin,crypto&workPlace=remote" -H "X-RapidAPI-Key: YOUR_API_KEY" -H "X-RapidAPI-Host: daily-international-job-postings.p.rapidapi.com"
  

• Jobs from Microsoft in the USA:

  curl -X GET "https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/count?countryCode=us&company=Microsoft" -H "X-RapidAPI-Key: YOUR_API_KEY" -H "X-RapidAPI-Host: daily-international-job-postings.p.rapidapi.com"
  

• Jobs for 'Chief ... Officer' (CxO) level in the USA:

  curl -X GET "https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/count?countryCode=us&careerLevel=Chief" -H "X-RapidAPI-Key: YOUR_API_KEY" -H "X-RapidAPI-Host: daily-international-job-postings.p.rapidapi.com"
  

1. Subscribe to the Basic plan of the Job Postings API on RapidAPI. It has no hard monthly limit - requests above the included quota are billed as overage (see Errors & billing).
2. Copy your key from the RapidAPI listing → Endpoints tab → code snippet → value of X-RapidAPI-Key - one key per RapidAPI application.
3. Make your first call. Replace YOUR_API_KEY with your key. A successful call returns HTTP 200.

curl

curl --request GET \
  --url 'https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/search?countryCode=us&title=developer' \
  --header 'X-RapidAPI-Key: YOUR_API_KEY' \
  --header 'X-RapidAPI-Host: daily-international-job-postings.p.rapidapi.com'

Python

import requests

url = "https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/search"
params = {"countryCode": "us", "title": "developer"}
headers = {
    "X-RapidAPI-Key": "YOUR_API_KEY",
    "X-RapidAPI-Host": "daily-international-job-postings.p.rapidapi.com",
}

response = requests.get(url, params=params, headers=headers, timeout=30)
response.raise_for_status()
print(response.json())

JavaScript

// Node.js 18+ or browser
const url = new URL('https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/search');
url.search = new URLSearchParams({ 'countryCode': 'us', 'title': 'developer' });

const response = await fetch(url, {
  headers: {
    'X-RapidAPI-Key': 'YOUR_API_KEY',
    'X-RapidAPI-Host': 'daily-international-job-postings.p.rapidapi.com',
  },
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
console.log(await response.json());

Java

// Java 11+
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;

public class TechmapExample {
    public static void main(String[] args) throws Exception {
        HttpRequest request = HttpRequest.newBuilder()
            .uri(URI.create("https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/search?countryCode=us&title=developer"))
            .header("X-RapidAPI-Key", "YOUR_API_KEY")
            .header("X-RapidAPI-Host", "daily-international-job-postings.p.rapidapi.com")
            .GET()
            .build();
        HttpResponse<String> response = HttpClient.newHttpClient()
            .send(request, HttpResponse.BodyHandlers.ofString());
        if (response.statusCode() != 200) throw new RuntimeException(response.statusCode() + ": " + response.body());
        System.out.println(response.body());
    }
}

Getting an error instead? See Errors & billing.

Requests are authenticated and billed by the marketplace you subscribe through. The base URL, the key and the plans depend on that marketplace.

RapidAPI

• Base URL: https://daily-international-job-postings.p.rapidapi.com
• Key: header X-RapidAPI-Key: YOUR_API_KEY
• Host (optional): header X-RapidAPI-Host: daily-international-job-postings.p.rapidapi.com
• Alternative: query parameter rapidapi-key=YOUR_API_KEY in the URL instead of the header
• Where to find the key: RapidAPI listing → Endpoints tab → code snippet → value of X-RapidAPI-Key - one key per RapidAPI application (see RapidAPI docs).
• Plans and prices: RapidAPI pricing page
• Calling the backend directly (without RapidAPI) returns 401.

All errors return JSON with a message field.

Example: endpoint not included in your plan (403)

{
  "message": "Forbidden request to the API - this endpoint is not included in your plan. It is included from the Pro plan on.",
  "requiredPlan": "Pro",
  "pricingUrl": "https://rapidapi.com/techmap-io-techmap-io-default/api/daily-international-job-postings/pricing"
}

Plans, included requests and overage: Errors & billing.

• 2026-10-06 (v2.7.2): A partial answer from the search backend (some index shards failed or timed out) now returns 503 instead of a 200 with incomplete results and a too-low totalCount. A 200 response is always complete, so you can safely treat missing postings as removed.
• 2026-10-03 (v2.7.1): Documentation release. Unknown countryCode values (e.g. zz, 00) and invalid dates or date ranges now return 400 with a clear message. All error responses now return valid JSON with a message field (some were plain text before). Added Quickstart, How to authenticate (per marketplace) and Errors & billing. Fixed the server URL (https://daily-international-job-postings.p.rapidapi.com) and added security schemes (X-RapidAPI-Key + X-RapidAPI-Host). A 403 for an endpoint not included in your plan now returns JSON with message, requiredPlan and pricingUrl.
• 2026-10-01 (v2.7): Added sort parameter (sort=newest or sort=oldest) to get the most recently collected job postings first. Works with page-based and cursor-based pagination. ⚠️ Note: the default is still oldest. With sort=newest, new job postings arriving between requests shift the page-based results (postings can repeat or be skipped across pages) - use cursor for complete, stable paging. Temporary search backend errors now return 503 (retry later) instead of passing on the backend status (e.g. a misleading 404), and an invalid countryCode or date returns 400 instead of 404. The duplicate filter is documented as isDuplicate (the spelling IsDuplicate from earlier docs keeps working).
• 2026-06-03 (v2.6): Fixed Boolean prefix operators (+/-) not applying correctly with multiple comma-separated values. Multiple values per field now use AND logic between fields and OR logic within a field.
• 2026-02-07 (v2.5): Added cursor parameter for cursor-based pagination.
• 2025-04-22 (v2.4): Added isDuplicate parameter for excluding potential duplicates.
• 2025-03-24 (v2.3): Added date range parameter for querying specific time periods.
• 2025-03-14 (v2.2): Added format parameter for output in json, csv, rss, atom, xml, and parquet.
• 2025-01-23 (v2.1): Added count endpoint.

Search and count job postings with the same filters.

Values and statistics of fields - to find valid filter values. Included from the Pro plan on.