Findwork API

Name: Findwork API
Brand: Findwork API
Availability: InStock

✓ Official Vendor SpecHR recruitingRecruiting AtsapiKey1 EndpointsREST

For Agents

Search aggregated tech and remote job listings via a single GET /jobs endpoint authenticated with a Token API key.

Install Jentic One Beta

Connect the Findwork API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Findwork API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Findwork API.

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

GET STARTED

Start building with Findwork API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Findwork API for, with concrete tasks.

★ 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.

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.

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.

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.

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

1 endpoints — 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.

METHOD

PATH

DESCRIPTION

GET

/jobs

Search aggregated tech and remote job listings

GET

/jobs

Search aggregated tech and remote job listings

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Findwork token API keys are stored encrypted in the Jentic vault. Agents receive scoped references; the raw token never appears in the Authorization header that the agent itself sees.

Intent-based discovery

Agents search Jentic by intent (for example find remote python jobs) and Jentic returns the Findwork GET /jobs operation with its query parameter schema, so the agent does not need to read the API docs.

Time to first call

Direct Findwork integration: a few hours for a wrapper. Through Jentic: under fifteen minutes - search, load, execute.

FAQs

Specific to using Findwork API through Jentic.

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.