RSS feeds for job searches

Every job search has a public RSS 2.0 feed at https://trawle.com/jobs.rss. No account or API key is required. Copy a search URL from the website and replace its path with /jobs.rss, keeping the query string.

For example, remote frontend jobs open to people in Copenhagen:

https://trawle.com/jobs.rss?role=frontend-engineer&where=2618425&workplace=remote

Paste that URL into a feed reader, n8n's RSS Feed Read node, or an RSS trigger in Zapier or IFTTT.

Filters and ordering

The feed uses the website's compact URL filters: q, role, field, where, company, workplace, seniority, type, lang, salary, currency, pay, posted, reposts and agencies. Lists are comma-separated; salary ranges look like 60000- or 60000-90000.

• By default, the feed contains up to 50 open, original postings first seen in the last seven days. Withheld postings and superseded-board duplicates are hidden, just as in search.
• Use posted=1d, 3d, 7d or 30d to change the window. Use reposts=only if you explicitly want reposted jobs instead of originals.
• Entries are always ordered by when Trawle first saw them, newest first, with stable IDs breaking ties. Employer-supplied posting dates cannot move an old job to the top.
• sort=pay retains the website's requirement for listed annual pay, but feeds still use chronological ordering.
• saved does not load a private saved search: the filters must be present in the URL.
• Malformed filter values are treated as on the website; filter lists above the API's size limits return HTTP 400.

An empty search returns a valid feed with no entries. Broad feeds include only the newest 50 matches; they are not a complete export. For reliable incremental collection or more results, use the JSON API's pagination and nextSince.

Identity, links and refreshes

Each entry's GUID is urn:uuid:<job ID>. Editing a job's title or application URL does not create a new entry. pubDate is Trawle's firstSeenAt, not the employer's posting date. The entry links directly to the employer's application page and includes a Trawle details link and attribution.

The data refreshes daily: scans start at 05:00 UTC, enrichment is dispatched at 09:00 UTC, and finalize runs at 13:00 UTC. Outside that window, CDN caching expires at the next 05:00 scan. During the window, caching lasts at most five minutes. The response provides an ETag; feed readers can send If-None-Match and receive HTTP 304 when nothing has changed.

Polling once a day is normally enough. The feed shares the public API's per-IP rate limit. Keep the “Data by Trawle” attribution and employer application link when displaying entries elsewhere.