providers/claude/plugin/skills/lever/SKILL.md
Lever integration via Apideck's ATS unified API — same methods work across every connector in ATS, switch by changing `serviceId`. Use when the user wants to read, write, or sync jobs, applicants, and applications in Lever. Routes through Apideck with serviceId "lever".
npx skillsauth add apideck-libraries/api-skills leverInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Access Lever through Apideck's ATS unified API — one of 11 ATS connectors that share the same method surface. Code you write here ports to Greenhouse, Workday, Workable and 7 other ATS connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Lever plumbing.
leverActivate this skill when the user explicitly wants to work with Lever — for example, "list open jobs in Lever" or "move an applicant through stages in Lever". This skill teaches the agent:
serviceId to pass on every call (lever)For the full method surface (parameters, pagination, filtering), use your language SDK skill:
apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-restFor the raw OpenAPI spec:
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
// List applicants in Lever
const { data } = await apideck.ats.applicants.list({
serviceId: "lever",
});
The Apideck ATS unified API exposes the same methods for every connector in its catalog. Switching from Lever to another ATS connector is a one-string change — no rewrite, no new SDK.
// Today — Lever
await apideck.ats.applicants.list({ serviceId: "lever" });
// Tomorrow — same code, different connector
await apideck.ats.applicants.list({ serviceId: "greenhouse" });
await apideck.ats.applicants.list({ serviceId: "workday" });
This is the compounding advantage of using Apideck over integrating Lever directly: code against the unified ATS API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
Lever is a recruiting platform with strong pipeline tooling. Apideck maps its opportunity-centric model.
| Lever entity | Apideck ATS resource |
|---|---|
| Posting | jobs |
| Opportunity | applicants |
| Application (Opportunity on a Posting) | applications |
| Stage | exposed via applications.current_stage |
const { data } = await apideck.ats.applicants.create({
serviceId: "lever",
applicant: {
first_name: "Morgan",
last_name: "Lee",
emails: [{ email: "[email protected]", type: "personal" }],
source: { name: "LinkedIn" },
},
});
When an endpoint isn't covered by the ATS unified API, use Apideck's Proxy to call Lever directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Lever's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: lever" \
-H "x-apideck-downstream-url: <target endpoint on Lever>" \
-H "x-apideck-downstream-method: GET"
See Lever's API docs for available endpoints.
Other ATS connectors that share this unified API surface (same method signatures, just change serviceId):
greenhouse, workday, workable (beta), bullhorn-ats (beta), teamtailor (beta), freshteam, jobadder (beta), recruitee, and 2 more.
apideck-connector-coverage — programmatic coverage checksapideck-best-practices — architecture, Vault, pagination, error handlingapideck-node — TypeScript / Node SDK patternsdevelopment
Jira Teams via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Teams's native API. Use when the user wants to call Jira Teams (no unified API resource mapping). Routes through Apideck with serviceId "jira-teams".
development
Jira Service Desk via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Service Desk's native API. Use when the user wants to call Jira Service Desk (no unified API resource mapping). Routes through Apideck with serviceId "jira-service-desk".
development
Jira Data Center via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to Jira Data Center's native API. Use when the user wants to call Jira Data Center (no unified API resource mapping). Routes through Apideck with serviceId "jira-data-center".
development
JetBrains YouTrack via Apideck's Proxy API + managed Vault auth — Apideck handles auth and proxies HTTP calls to JetBrains YouTrack's native API. Use when the user wants to call JetBrains YouTrack (no unified API resource mapping). Routes through Apideck with serviceId "jetbrains-youtrack".