Indeed

Indeed email apply parsing, Apply API status, and compliance considerations for job board sourcing.

Indeed is a primary sourcing channel for InsightHire customers. Today the production path is email apply parsing — each position receives a unique inbound address and Indeed application notification emails are parsed into candidates automatically. A full Indeed Apply API integration exists in the codebase but is not the default customer-facing catalog entry.

Two integration paths

Platform admin note: the indeed slug in platform_integration_settings is intentionally enabled: false because email apply covers most customers today. The Apply API UI remains at /dashboard/integrations/indeed for early adopters.

Email apply (recommended)

How addressing works

Each open position gets a unique token:

pos_{12-char-nanoid}@in.insighthire.com

• Token stored as positions.inboundEmailToken.
• Domain configurable via INBOUND_EMAIL_DOMAIN (default in.insighthire.com).
• Visible on the position detail page for recruiters configuring Indeed job posts.

Because the To address encodes the position, InsightHire knows which role the candidate applied to — no fuzzy job-title matching.

Indeed job post setup

When posting on Indeed:

1. Copy the position's Indeed apply email from InsightHire.
2. In Indeed Employer, set Application delivery method to Email.
3. Paste the InsightHire inbound address as the application email.
4. Publish the job.

When a candidate applies, Indeed sends a notification email to that address.

Email parsing pipeline

Inbound mail hits the API inbound handler → inbound-email.service.ts:

1. Source detection — sender/subject/body patterns (indeed.com, @indeedemail.com, etc.).
2. Indeed parser — indeed-parser.service.ts extracts:
   • Candidate name, email, phone
   • Job title (for logging)
   • Resume attachment (PDF)
   • Indeed application URL and candidate ID when present
3. Resume handling — PDF uploaded to S3; optional text extraction for contact info.
4. Indeed resume fetcher — supplementary resume retrieval when email link available.
5. Candidate creation — profile + application with source INDEED; journey invite sent if configured.

Parse confidence is scored 0–100. Low-confidence parses are logged for ops review.

Supported email sources

The inbound parser also recognizes (with lower priority than dedicated integrations):

• LinkedIn notification forwards
• ZipRecruiter
• Glassdoor
• Manual recruiter forwards

Indeed-sourced applications are tagged with externalSource: INDEED.

Duplicate and edge handling

Apply API path (advanced)

For employers with Indeed Developer / Employer API access:

Settings path

/dashboard/integrations/indeed

Configuration fields

Stored in ats_integrations with platform INDEED. API key field encodes clientId:clientSecret.

OAuth scopes

employer_access manage_candidates read_applications

Authorization URL: https://secure.indeed.com/oauth/v2/authorize

Token exchange: https://apis.indeed.com/oauth/v2/tokens

API operations

Requires Professional+ subscription (enforceATSAccess).

Apply API status

Contact InsightHire support or Indeed partner team to enable Apply API for your employer account.

Compliance

Candidate consent and data handling

• Indeed applications contain PII (name, email, phone, resume). InsightHire stores these under the org's tenant with standard retention and export controls.
• Resume files land in org-scoped S3 prefixes: organizations/{orgId}/candidates/{candidateId}/resume/.
• Journey invites sent after apply must comply with your organization's messaging and consent policies.

EEO and sourcing attribution

• Source is recorded as INDEED (or INDEED_SPONSORED when detected in API path) for analytics and compliance reporting.
• Use Settings → Compliance (when DEI module enabled) for adverse impact and source reporting — Indeed applies flow into the same candidate pipeline as careers-page applies.

Email security

• Inbound domain (in.insighthire.com) is operated by InsightHire; only position-scoped tokens route mail to the correct tenant.
• Do not share one position email across multiple Indeed jobs — each role should have its own token for accurate attribution.

Indeed employer policies

• Follow Indeed Employer Guidelines for job content, apply methods, and candidate communication.
• Email apply must use the address Indeed sends applications to — do not intercept or modify candidate submissions outside Indeed's flow.

Troubleshooting

Related

• Integrations overview
• ATS imports — for Greenhouse/Workday alongside Indeed sourcing