canonical: https://jentic.com/apis/findwork.dev/findwork # Findwork API The Findwork API exposes a single endpoint that returns aggregated tech and remote job listings sourced from multiple boards, returned as JSON over Django REST Framework. Authentication is performed by sending an Authorization header with the value Token YOUR_API_KEY. The API is used by job aggregators, agent-driven job search assistants, and dashboards that surface relevant tech roles without scraping individual ATS sites or maintaining their own crawler. ## For AI agents Search aggregated tech and remote job listings via a single GET /jobs endpoint authenticated with a Token API key. ## Scope Does not handle job posting, application submission, or applicant tracking - use for searching aggregated tech and remote job listings only. ## Capabilities - Search aggregated tech job listings filtered by keyword, location, and remote flag - Return company name, role, and application URL for each matching listing - Page through job results to power dashboards and digest emails - Surface listings sourced across multiple boards in a single normalised response - Drive an agent loop that re-queries on a schedule for new matches ## Use cases ### Personal Job Search Assistant Job seekers can have an agent call GET /jobs with their saved keywords on a schedule and email a daily digest of new matches. Because Findwork normalises listings across multiple boards into a single response, the assistant does not need to integrate with each ATS individually and the seeker sees fewer duplicates. Example prompt: Call GET /jobs with the saved keyword and remote=true, dedupe against yesterday's results, and email the new listings. ### Remote-Only Talent Dashboard Talent teams hiring remote tech staff can build a dashboard backed by GET /jobs filtered to remote roles in their stack. The agent walks the result pages and renders a leaderboard of competing job posts, helping the team benchmark their own listing against the live market. Example prompt: Page through GET /jobs with remote=true and a stack filter, rank by company posting frequency, and render the dashboard. ### Newsletter Curation Tech newsletter operators can have an agent pull GET /jobs filtered by their audience's stack and surface a weekly top-ten section. Findwork's aggregation means a single API call replaces five or six per-board scrapers and the curator can spend their time on commentary rather than collection. Example prompt: Call GET /jobs with the newsletter's keyword set, rank by recency and prestige signals, and select ten for the issue. ### AI Agent Findwork Integration via Jentic An agent connected to Jentic can search by intent (for example find remote python jobs) and Jentic returns the Findwork GET /jobs operation along with its query parameters. The Token API key lives in the vault, so the agent never embeds the credential. Integration drops from a one-day setup to a single search-load-execute call. Example prompt: Search Jentic for find remote tech jobs, load GET /jobs, and execute with search and remote query parameters while Jentic injects the token. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/jobs` | Search aggregated tech and remote job listings | ## Key resources - **Jobs** — Aggregated tech job listings filterable by keyword, location, and remote flag ## Why Jentic - **Setup:** Wiring the Findwork API by hand means sending the token in the Authorization header, pointing at findwork.dev/api, and constructing the query filters on its single job-search route yourself. Through Jentic you install once, import the Findwork API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Findwork exposes a single read-only job-search operation with its target carried as query filters rather than an owned-resource path id, so scope the agent to that one search operation and nothing else. Because you choose the allowed operation, the agent only reads the listings the search returns. - **Credential handling:** Your Findwork token is stored once, encrypted, by your own Jentic One instance and injected at execution time. The raw token never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find remote python jobs', and Jentic returns the Findwork job-search operation with its query parameter schema, so the agent does not need to read the API docs. ## Related APIs - **Adzuna API** — Broader job aggregator covering non-tech roles in addition to tech - **Careerjet API** — Global job search aggregator with deeper international coverage - **Greenhouse Harvest API** — Native ATS API for the hiring side of a Findwork listing ## FAQ ### What authentication does the Findwork API use? Findwork uses a token API key sent in the Authorization header in the format Token YOUR_API_KEY. Through Jentic the token lives in the encrypted vault and is injected at execution; the agent only ever sees a vault reference. ### Can I filter Findwork results to remote roles only? Yes. GET /jobs accepts a remote query parameter that filters to listings flagged as remote. Combine it with the search parameter to narrow to a specific stack such as Python or React. ### What are the rate limits for the Findwork API? Findwork applies per-API-key throttling and the spec does not publish a fixed RPS. Free keys are limited more aggressively than commercial keys. Agents should respect 429 responses with exponential backoff and cache results when polling on a schedule. ### How do I find remote Python jobs through Jentic? Search Jentic for find remote python jobs, load GET /jobs, and execute with search=python and remote=true. Jentic injects the token from the vault and Findwork returns the matching listings. ### Does Findwork provide application URLs for each listing? Yes. Each result in the GET /jobs response includes the source application URL, so an agent can present the apply link directly without redirecting through the Findwork site. ### Is the Findwork API free to use? Findwork has a free developer tier with a daily request quota and paid tiers for higher volume. Both tiers use the same single GET /jobs endpoint and the same Token authentication scheme. ### Can I limit what my agent is allowed to do with the Findwork API? Yes. Findwork exposes a single read-only job-search operation, GET /jobs, and because Jentic One is self-hosted your own rules decide which operations and credentials the agent may use. You can scope the agent to that one search operation and nothing else, so it can only read the listings a GET /jobs query returns and cannot reach any other route. The target is carried as query filters such as search and remote rather than an owned-resource path, so there is no write or delete surface for the agent to touch.