Use the Recruitee CLI from KosmoKrator to call Recruitee tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
Recruitee can be configured headlessly with `kosmokrator integrations:configure recruitee`.
# Install KosmoKrator first if it is not available on PATH.curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash# Configure and verify this integration.kosmokrator integrations:configure recruitee --set access_token="$RECRUITEE_ACCESS_TOKEN" --set company_id="$RECRUITEE_COMPANY_ID" --enable --read allow --write ask --jsonkosmokrator integrations:doctor recruitee --jsonkosmokrator integrations:status --json
Credentials
Authentication type: Bearer tokenbearer_token. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
access_token
RECRUITEE_ACCESS_TOKEN
Secret secret
yes
Access Token
company_id
RECRUITEE_COMPANY_ID
Text text
yes
Company ID
url
RECRUITEE_URL
URL url
no
API Base URL
Call Recruitee Headlessly
Use the generic call form when another coding CLI or script needs a stable universal interface.
Every function below can be called headlessly. The generic form is stable across all integrations;
the provider shortcut is shorter but specific to Recruitee.
recruitee.recruitee_list_offers
Read read
List job offers (open positions) from Recruitee. Returns paginated results with offer titles, statuses, and metadata. Filter by status to see only open, closed, or draft positions.
Use these parameter tables when building CLI payloads without calling integrations:schema first.
recruitee.recruitee_list_offers
List job offers (open positions) from Recruitee. Returns paginated results with offer titles, statuses, and metadata. Filter by status to see only open, closed, or draft positions.
Headless calls still follow the integration read/write permission policy. Configure read/write defaults
with integrations:configure. Add --force only for trusted automation that should bypass that policy.