Reed Job Search API

Name: Reed Job Search API
Brand: Reed Job Search API
Availability: InStock

✓ Official Vendor SpecHR recruitingRecruiting Atsbasic2 EndpointsREST

For Agents

Programmatically search for jobs, get job details. Covers 2 operations with basic authentication.

Install Jentic One Beta

Connect the Reed Job Search API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Reed Job Search 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Freed.co.uk%2Freed" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Freed.co.uk%2Freed" | 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 Reed Job Search API.

Search for jobs

Get job details

Integrate Reed Job Search API into automated workflows

Query and filter Reed Job Search API records by parameters

GET STARTED

Start building with Reed Job Search API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Reed Job Search API for, with concrete tasks.

★ HR and Recruiting Operations

Use the Reed Job Search API to perform hr recruiting operations programmatically. The API provides 2 endpoints covering core functionality including search for jobs, get job details.

Call GET /search to search for jobs

Data Retrieval and Monitoring

Query Reed Job Search API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary Reed Job Search API endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call Reed Job Search API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Search Jentic for 'search for jobs', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — reed.

METHOD

PATH

DESCRIPTION

GET

/search

Search for jobs

GET

/jobs/{jobId}

Get job details

GET

/search

Search for jobs

GET

/jobs/{jobId}

Get job details

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Reed Job Search API by hand means encoding your key into HTTP basic auth on every request and handling failures against the www.reed.co.uk host yourself. Through Jentic you install once, import the Reed Job Search API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Reed Job Search API puts the job id in the URL path (/jobs/{jobId}) alongside a /search endpoint, so a rule can pin your agent to reading job details and searching listings. Both operations are read-only, and the agent runs only the operations you have chosen to allow.

Credential isolation

Your Reed Job Search API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'search for jobs' or 'get details of a job', and Jentic returns the matching Reed Job Search API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Reed Job Search API through Jentic.

What authentication does the Reed Job Search API use?

The Reed Job Search API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I search for jobs with the Reed Job Search API?

Yes. Use the GET /search endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Reed Job Search API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I search for jobs through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search for jobs'. Jentic returns the matching Reed Job Search API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Reed Job Search API have?

The Reed Job Search API exposes 2 endpoints covering jobs operations.

Can I limit what my agent is allowed to do with the Reed Job Search API?

Yes. Because Jentic One is self-hosted, you set the rules that decide which Reed Job Search API operations and credentials your agent may use. The Reed Job Search API exposes only two read-only operations, GET /search for finding job listings and GET /jobs/{jobId} for retrieving details of a single job, so you can pin your agent to searching listings, reading job details, or both. The agent runs only the operations you have chosen to allow, and your stored key is injected at execution time rather than exposed in the agent's context.

Reed Job Search API

Connect the Reed Job Search API to your agent

Capabilities

Start building with Reed Job Search API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs