Workable API

Name: Workable API
Brand: Workable API
Availability: InStock

✓ Official Vendor SpecHR recruitingRecruiting Atsbearer31 EndpointsREST

For Agents

Programmatically get account info, list members. Covers 31 operations with bearer authentication.

Install Jentic One Beta

Connect the Workable API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Workable 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 Workable API.

Get account info

List members

Update member

Invite member

GET STARTED

Start building with Workable API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Workable API for, with concrete tasks.

★ HR and Recruiting Operations

Use the Workable API to perform hr recruiting operations programmatically. The API provides 31 endpoints covering core functionality including get account info, list members, update member.

Call GET /accounts to get account info

Automated Account Management

Automate account operations by combining multiple Workable API endpoints. Agents can list members and then update member in a single workflow.

Call GET /members to list members, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Workable 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 bearer tokens manually.

Search Jentic for 'get account info', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

31 endpoints — workable recruiting and hr api.

METHOD

PATH

DESCRIPTION

GET

/accounts

Get account info

GET

/members

List members

PUT

/members

Update member

POST

/members/invite

Invite member

DELETE

/members/{id}

Remove member

POST

/departments

Create department

GET

/departments

List departments

GET

/stages

List stages

GET

/accounts

Get account info

GET

/members

List members

PUT

/members

Update member

POST

/members/invite

Invite member

DELETE

/members/{id}

Remove member

POST

/departments

Create department

Why Jentic?

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

Credential isolation

Your Workable token 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 'get account info' or 'list departments', and Jentic returns the matching Workable operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Workable API through Jentic.

What authentication does the Workable API use?

The Workable API uses a Bearer token in the Authorization header. 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 get account info with the Workable API?

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

What are the rate limits for the Workable 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 get account info through Jentic?

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

How many endpoints does the Workable API have?

The Workable API exposes 31 endpoints covering account, candidates, hr operations.

Can I limit what my agent is allowed to do with the Workable API?

Yes. Jentic One runs self-hosted, so your own rules decide which Workable operations and credentials the agent may use. Because Workable puts the member id in the URL path (/members/{id}), you can pin the agent to read-only calls like GET /members and GET /departments while excluding destructive operations such as DELETE /members/{id} unless you explicitly add them. The agent can only invoke the operations you have allowed, and the stored Workable token is injected at execution time rather than exposed to the agent.

Workable API

Connect the Workable API to your agent

Capabilities

Start building with Workable API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs