OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
Candidate profiles are returned by the v3 collection endpoint; applications, attachments, education and employment use separate resources. All list endpoints require a Site Admin authorizing user.
Greenhouse Harvest v3 list candidates ↗
List candidates: cursor, per_page, updated_at, private and separately linked resources · Checked 2026-10-16
Greenhouse Harvest v3 authentication ↗
Step 2 About sub; 403 troubleshooting · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
Complete the documented pagination to retrieve the permitted current collection; a page alone is not a complete copy. All list endpoints require a Site Admin authorizing user.
Greenhouse Harvest v3 list candidates ↗
List candidates: cursor, per_page, updated_at, private and separately linked resources · Checked 2026-10-16
Greenhouse Harvest v3 authentication ↗
Step 2 About sub; 403 troubleshooting · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
Candidate filters include update/creation time, email, tag and selected custom-field options. Private records still depend on caller access.
Greenhouse Harvest v3 list candidates ↗
List candidates: cursor, per_page, updated_at, private and separately linked resources · Checked 2026-10-16
Access cost barrier -
-
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
The reviewed API documentation establishes a technical route; lowest-paid-plan entitlement, partner charges and fixed API access fees remain unresolved.
Greenhouse Harvest v3 authentication ↗
Authentication methods by integration type; custom integrations; Site Admin list requirement · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 5.0/10
Separate provider consent or partner agreement required
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
Chosen partner applications require a signed Greenhouse partnership agreement and provider-issued OAuth credentials. Customer client credentials are limited to that customer’s own integration.
Greenhouse Harvest partner OAuth requirements ↗
Signed partnership agreement; credentials from Partner Support; steps 1, 6 and 7 · Checked 2026-10-16
Greenhouse Harvest v3 authentication ↗
Authentication methods by integration type; custom integrations; Site Admin list requirement · Checked 2026-10-16
Downstream permission -
-
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
The authentication and operation guides do not establish applicable processing, AI-use or redistribution rights.
Greenhouse Harvest v3 authentication ↗
Authentication methods by integration type; custom integrations; Site Admin list requirement · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
POST /v3/candidates creates a profile and can create its first application. Broader update coverage is not established by this assessed operation.
Greenhouse Harvest v3 create candidate ↗
POST /v3/candidates: required profile fields; optional application; validation responses · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
A chosen provider integration must complete the disclosed approval route before customer authorization.
Greenhouse Harvest partner OAuth requirements ↗
Signed partnership agreement; credentials from Partner Support; steps 1, 6 and 7 · Checked 2026-10-16
Greenhouse Harvest v3 authentication ↗
Authentication methods by integration type; custom integrations; Site Admin list requirement · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
Poll updated_at filters with overlap and periodic complete traversals; the collection is current state rather than a retained change log.
Greenhouse Harvest v3 list candidates ↗
List candidates: cursor, per_page, updated_at, private and separately linked resources · Checked 2026-10-16
Limit visibility 7.5/10
Service-specific limits disclosed in runtime headers
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
Harvest v3 uses separate custom/partner limits in 30-second windows, with token issuance on 60-second windows. Actual capacity comes from rate headers; honor Retry-After on 429.
Greenhouse Harvest v3 rate limiting ↗
30-second fixed window; separate 60-second token window; X-RateLimit headers; Retry-After · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
updated_at identifies changed profiles; deleted identities and deleted payloads are not established by this collection.
Greenhouse Harvest v3 list candidates ↗
List candidates: cursor, per_page, updated_at, private and separately linked resources · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
Restart candidate pagination without change filters to rebuild permitted current profiles; deleted payloads and intermediate history are not recovered.
Greenhouse Harvest v3 list candidates ↗
List candidates: cursor, per_page, updated_at, private and separately linked resources · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
The API returns structured records that a permitted client can retain as a customer-held copy.
Greenhouse Harvest v3 list candidates ↗
List candidates: cursor, per_page, updated_at, private and separately linked resources · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
Current API retrieval does not establish contractual retrieval rights after cancellation.
Greenhouse Harvest v3 list candidates ↗
List candidates: cursor, per_page, updated_at, private and separately linked resources · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
Portable records cover the declared collection. Files, full activity history, workflow configuration and a whole-product restore remain outside the established scope.
Greenhouse Harvest v3 list candidates ↗
List candidates: cursor, per_page, updated_at, private and separately linked resources · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
Customers can implement logic in an external API client; native workflow authoring or portable native definitions are not established (client code is a separate artifact).
Greenhouse Harvest v3 authentication ↗
Authentication methods by integration type; custom integrations; Site Admin list requirement · Checked 2026-10-16
Rights to custom logic -
-
Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included.
The reviewed API guides do not establish ownership, reusable export or independent execution rights for native workflow artifacts.
Greenhouse Harvest v3 authentication ↗
Authentication methods by integration type; custom integrations; Site Admin list requirement · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Chosen partner applications require a signed Greenhouse partnership agreement and provider-issued OAuth credentials. Customer client credentials are limited to that customer’s own integration. All list endpoints require a Site Admin authorizing user.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Candidate profiles are returned by the v3 collection endpoint; applications, attachments, education and employment use separate resources. Complete the documented pagination to retrieve the permitted current collection; a page alone is not a complete copy. Candidate filters include update/creation time, email, tag and selected custom-field options. Private records still depend on caller access. Authorize collection reads as a Site Admin.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Approved Harvest v3 partner application | OAuth 2.0 | Integration provider | Yes | partner agreement | 2026-10-16 |
| Customer-only Harvest v3 integration | OAuth client credentials | Customer | No | customer authorization | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The reviewed API documentation establishes a technical route; lowest-paid-plan entitlement, partner charges and fixed API access fees remain unresolved.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
POST /v3/candidates creates a profile and can create its first application. Broader update coverage is not established by this assessed operation.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Poll updated_at filters with overlap and periodic complete traversals; the collection is current state rather than a retained change log. updated_at identifies changed profiles; deleted identities and deleted payloads are not established by this collection. Restart candidate pagination without change filters to rebuild permitted current profiles; deleted payloads and intermediate history are not recovered. Harvest v3 uses separate custom/partner limits in 30-second windows, with token issuance on 60-second windows. Actual capacity comes from rate headers; honor Retry-After on 429.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates identified; deletion capture not establishedGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. updated_at identifies changed profiles; deleted identities and deleted payloads are not established by this collection. | Greenhouse Harvest v3 list candidates ↗List candidates: cursor, per_page, updated_at, private and separately linked resourcesChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. Restart candidate pagination without change filters to rebuild permitted current profiles; deleted payloads and intermediate history are not recovered. | Greenhouse Harvest v3 list candidates ↗List candidates: cursor, per_page, updated_at, private and separately linked resourcesChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Portable records cover the declared collection. Files, full activity history, workflow configuration and a whole-product restore remain outside the established scope. Current API retrieval does not establish contractual retrieval rights after cancellation.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can implement logic in an external API client; native workflow authoring or portable native definitions are not established (client code is a separate artifact). The reviewed API guides do not establish ownership, reusable export or independent execution rights for native workflow artifacts.
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. Candidate profiles are returned by the v3 collection endpoint; applications, attachments, education and employment use separate resources. All list endpoints require a Site Admin authorizing user. | Greenhouse Harvest v3 list candidates ↗List candidates: cursor, per_page, updated_at, private and separately linked resourcesChecked 2026-10-16 Greenhouse Harvest v3 authentication ↗Step 2 About sub; 403 troubleshootingChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. Complete the documented pagination to retrieve the permitted current collection; a page alone is not a complete copy. All list endpoints require a Site Admin authorizing user. | Greenhouse Harvest v3 list candidates ↗List candidates: cursor, per_page, updated_at, private and separately linked resourcesChecked 2026-10-16 Greenhouse Harvest v3 authentication ↗Step 2 About sub; 403 troubleshootingChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. Candidate filters include update/creation time, email, tag and selected custom-field options. Private records still depend on caller access. | Greenhouse Harvest v3 list candidates ↗List candidates: cursor, per_page, updated_at, private and separately linked resourcesChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. Chosen partner applications require a signed Greenhouse partnership agreement and provider-issued OAuth credentials. Customer client credentials are limited to that customer’s own integration. | Greenhouse Harvest partner OAuth requirements ↗Signed partnership agreement; credentials from Partner Support; steps 1, 6 and 7Checked 2026-10-16 Greenhouse Harvest v3 authentication ↗Authentication methods by integration type; custom integrations; Site Admin list requirementChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. The reviewed API documentation establishes a technical route; lowest-paid-plan entitlement, partner charges and fixed API access fees remain unresolved. | Greenhouse Harvest v3 authentication ↗Authentication methods by integration type; custom integrations; Site Admin list requirementChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. The authentication and operation guides do not establish applicable processing, AI-use or redistribution rights. | Greenhouse Harvest v3 authentication ↗Authentication methods by integration type; custom integrations; Site Admin list requirementChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. POST /v3/candidates creates a profile and can create its first application. Broader update coverage is not established by this assessed operation. | Greenhouse Harvest v3 create candidate ↗POST /v3/candidates: required profile fields; optional application; validation responsesChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. A chosen provider integration must complete the disclosed approval route before customer authorization. | Greenhouse Harvest partner OAuth requirements ↗Signed partnership agreement; credentials from Partner Support; steps 1, 6 and 7Checked 2026-10-16 Greenhouse Harvest v3 authentication ↗Authentication methods by integration type; custom integrations; Site Admin list requirementChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. Poll updated_at filters with overlap and periodic complete traversals; the collection is current state rather than a retained change log. | Greenhouse Harvest v3 list candidates ↗List candidates: cursor, per_page, updated_at, private and separately linked resourcesChecked 2026-10-16 |
| How are integration limits disclosed? | Service-specific limits disclosed in runtime headersGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. Harvest v3 uses separate custom/partner limits in 30-second windows, with token issuance on 60-second windows. Actual capacity comes from rate headers; honor Retry-After on 429. | Greenhouse Harvest v3 rate limiting ↗30-second fixed window; separate 60-second token window; X-RateLimit headers; Retry-AfterChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. The API returns structured records that a permitted client can retain as a customer-held copy. | Greenhouse Harvest v3 list candidates ↗List candidates: cursor, per_page, updated_at, private and separately linked resourcesChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. Current API retrieval does not establish contractual retrieval rights after cancellation. | Greenhouse Harvest v3 list candidates ↗List candidates: cursor, per_page, updated_at, private and separately linked resourcesChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. Customers can implement logic in an external API client; native workflow authoring or portable native definitions are not established (client code is a separate artifact). | Greenhouse Harvest v3 authentication ↗Authentication methods by integration type; custom integrations; Site Admin list requirementChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Greenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. The reviewed API guides do not establish ownership, reusable export or independent execution rights for native workflow artifacts. | Greenhouse Harvest v3 authentication ↗Authentication methods by integration type; custom integrations; Site Admin list requirementChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedGreenhouse Recruiting / Harvest v3 candidate profile collection and candidate creation, using an approved partner OAuth application or a separate customer-only client-credentials integration; nested applications, attachments and other resources are not assumed included. Portable records cover the declared collection. Files, full activity history, workflow configuration and a whole-product restore remain outside the established scope. | Greenhouse Harvest v3 list candidates ↗List candidates: cursor, per_page, updated_at, private and separately linked resourcesChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Complete lowest-plan entitlement and fixed API fees
- Applicable downstream processing, AI-use and redistribution rights
- Contractual post-cancellation retrieval terms
- Native workflow artifact ownership, reusable export and independent execution
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.