Public API receiver
Three feeds. One attributed wire.
A live, browser-side view of recent remote vacancies from Remotive, Jobicy and Working Nomads, normalized for scanning but always linked back to the credited source.
The browser requests each public feed at most once per hour and caches the normalized result on this device. Records are never presented as Wramer vacancies.
Sources: Remotive · Jobicy · Working Nomads
What this receiver does—and does not do.
Wramer is a discovery layer, not an employer, recruiter or applicant-tracking system. The receiver reads public feeds, aligns a small set of fields and gives every record a visible source. It never turns an API item into a Wramer-owned vacancy.
Attribution stays attached
Remotive asks publishers to mention the platform and link to the supplied job URL. Jobicy likewise requires clear credit and direct source links. Wramer keeps both requirements visible in the feed and does the same for Working Nomads. Application buttons lead outward; Wramer does not collect applications or email addresses to unlock a listing.
The receiver checks slowly
Freshness does not require aggressive polling. Jobicy states that a few checks per day are sufficient and requests no more than hourly access. Wramer uses a one-hour device cache and makes one request per source when that cache expires. A manual retune inside the hour reuses the cache.
Normalization is intentionally small
The feed aligns title, company, location, category, source, date and destination. It does not rewrite descriptions, infer eligibility or claim that unlike fields mean the same thing. A location entered as Global by one source may follow different rules from an Anywhere label on another.
Live does not mean verified by Wramer
A current API response confirms only that the source supplied a record at that moment. Before applying, open the destination, confirm the employer domain, compare the location language and make sure the role is still active. Wramer’s verification guide provides a short routine.
Failure has a readable fallback
Public endpoints can be unavailable, rate-limited or blocked by a browser policy. If all three fail, Wramer leaves a dated editorial snapshot visible instead of presenting an empty console. That snapshot is clearly labeled and should be treated as an example, not a promise of current availability.