Quickstart

Sign up for a free account, then navigate to Settings → Integrations → API Keys to generate your key.

API keys start with ws_ and should be treated like a password - never commit them to source control.

The /quick_post endpoint creates a role, generates a career page posting, and publishes it live in one call:

curl -X POST https://worksignal.com/api/v1/quick_post \
  -H "Authorization: Bearer ws_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "role": {
      "title": "Senior Backend Engineer",
      "department": "Engineering",
      "description": "Build the core API and data pipeline.",
      "location": "Remote",
      "remote_policy": "remote",
      "salary_min": 150000,
      "salary_max": 200000
    }
  }'

A successful response returns the live job posting URL, role ID, and your career portal URL.

{
  "role": {
    "id": 42,
    "title": "Senior Backend Engineer",
    "status": "open"
  },
  "job_posting": {
    "id": 15,
    "slug": "senior-backend-engineer",
    "published": true,
    "public_url": "https://worksignal.com/careers/your-company/jobs/senior-backend-engineer"
  },
  "career_portal_url": "https://worksignal.com/careers/your-company"
}

The WorkSignal MCP server lets you manage hiring by talking to your AI tool in plain English. Pick your setup:

claude mcp add worksignal --transport stdio \
  -e WORKSIGNAL_API_KEY=ws_your_key_here \
  -- npx -y @worksignal/mcp-server

cursor mcp add worksignal "npx -y @worksignal/mcp-server" \
  -e WORKSIGNAL_API_KEY=ws_your_key_here

{
  "worksignal": {
    "command": "npx",
    "args": ["-y", "@worksignal/mcp-server"],
    "env": {
      "WORKSIGNAL_API_KEY": "ws_your_key_here"
    }
  }
}

Need more detail on MCP auth and OAuth flow? See the MCP setup guide.