ATS Integration Guide: Connecting EchoHire with Greenhouse, Lever & Workday

Overview

EchoHire integrates with all major ATS platforms via bi-directional API sync. This guide covers the three most common integrations: Greenhouse, Lever, and Workday. For each, we'll cover authentication, field mapping, webhook configuration, and common issues.

Greenhouse Integration

Authentication

Greenhouse uses API key authentication. You'll need to generate a Harvest API key from your Greenhouse account settings. EchoHire uses this key to read candidate data and write back scores and notes.

EchoHire uses the Harvest API key in the Authorization header as a Base64-encoded string (Basic auth scheme). Pass the API key followed by a colon, Base64-encode the result, and include it in every request to the Greenhouse Harvest API endpoint.

Field Mapping

EchoHire maps to the following Greenhouse fields by default:

• candidate.id → EchoHire candidate_id
• application.id → EchoHire application_id
• job.id → EchoHire job_id
• scorecard.overall_recommendation → EchoHire ai_score

Webhook Configuration

Configure webhooks in Greenhouse to notify EchoHire when candidates advance stages. Go to Configure → Dev Center → Web Hooks and add your EchoHire webhook URL.

Lever Integration

Authentication

Lever uses OAuth 2.0. You'll need to register EchoHire as an OAuth application in your Lever account and complete the authorization flow.

Key Differences from Greenhouse

Lever's data model is opportunity-centric rather than application-centric. This means:

• Candidates can have multiple opportunities (one per job)
• Stage changes are tracked at the opportunity level
• Feedback is attached to opportunities, not candidates

Workday Integration

Workday integration requires the Workday Recruiting module and SOAP API access. This is the most complex integration due to Workday's XML-based API.

Prerequisites

• Workday Recruiting module enabled
• Integration System User (ISU) account
• SOAP API credentials
• Workday tenant URL

Common Gotchas

Rate Limits

Greenhouse limits API calls to 50 per 10 seconds. EchoHire handles this automatically with exponential backoff, but be aware if you're building custom integrations.

Field Validation

ATS platforms have strict field validation. EchoHire scores (0-100) need to be mapped to each platform's native scoring scale before writing back.

Webhook Reliability

Webhooks can fail. Always implement idempotent handlers and verify webhook signatures to prevent duplicate processing.

Testing Your Integration

Use EchoHire's sandbox environment to test your integration before going live. The sandbox mirrors production behavior but uses test data that won't affect your ATS.