View as Markdown
Lever icon

Lever ACTION

Get Posting

Returns full details for a single job posting by ID, including its complete job description. Use this to read a specific role's description, requirements, and closing text — the response content object holds description/descriptionHtml, lists (e.g. requirements), and closing/closingHtml, plus salaryDescription, salaryRange, categories (team, department, location, commitment, level), state, and application urls. Use List Postings to find posting IDs. Example: call with postingId="<id>" → returns the posting with its full job description under content.description. See the documentation
  • Action
  • Read only
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Lever account once, then configure and run Get Posting from your backend or agent.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "lever-get-posting",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    lever: { authProvisionId: "apn_xxxxxxx" },
    postingId: "Posting ID",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Get Posting inputs
Property Type Description
postingId Posting ID string
The ID of the posting to retrieve. Use List Postings to find posting IDs.
Required

REFERENCE

Tool details

Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.

Registry key
lever-get-posting
Version
0.0.2
App
Lever
Authentication
OAuth
Read-only
Yes
Destructive
No
Open world
Yes