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
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
The authenticated API lists opportunity records as JSON. Public job postings are a separate feed.
Lever opportunity collection and mutation reference ↗
List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeleted · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
Follow opaque next/offset tokens; list pages contain at most 100 records.
Lever opportunity collection and mutation reference ↗
List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeleted · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
Opportunity filters include update-time ranges, stage and archive status.
Lever opportunity collection and mutation reference ↗
List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeleted · Checked 2026-10-16
Access cost barrier -
-
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
The reviewed API documentation establishes a technical route; lowest-paid-plan entitlement, partner charges and fixed API access fees remain unresolved.
Lever API authentication and opportunity operations ↗
Authentication; Pagination; Opportunities; Rate Limits; Webhooks · 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
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
Lever approves partner integrations and issues production OAuth credentials after review. Basic-auth customer keys are for internal workflows.
Lever partner product integration process ↗
Steps 1–4; Basic Auth for customer internal workflows; production OAuth credentials; customer feature requirements · Checked 2026-10-16
Downstream permission -
-
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
The authentication and operation guides do not establish applicable processing, AI-use or redistribution rights.
Lever API authentication and opportunity operations ↗
Authentication; Pagination; Opportunities; Rate Limits; Webhooks · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
The opportunity API documents create and update operations; mutations require the corresponding granted scopes.
Lever opportunity collection and mutation reference ↗
List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeleted · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
A chosen provider integration must complete the disclosed approval route before customer authorization.
Lever partner product integration process ↗
Steps 1–4; Basic Auth for customer internal workflows; production OAuth credentials; customer feature requirements · 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
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
Use update-time polling and event hints. An update filter covers more changes than the returned updatedAt field.
Lever opportunity collection and mutation reference ↗
List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeleted · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
Default per-key capacity is 10 requests/second, bursting to 20; defaults may vary. Use exponential backoff.
Lever API authentication and opportunity operations ↗
Authentication; Pagination; Opportunities; Rate Limits; Webhooks · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
Opportunity update filters and candidateDeleted webhook identities support changed/deleted recruiting records; retain opportunity/contact identity mapping.
Lever opportunity collection and mutation reference ↗
List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeleted · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
Re-run opportunity pagination to rebuild permitted current records; webhook redelivery is bounded and does not recover erased payloads.
Lever opportunity collection and mutation reference ↗
List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeleted · 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
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
Authorized opportunity JSON can be held by the customer.
Lever opportunity collection and mutation reference ↗
List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeleted · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
Current API retrieval does not establish contractual retrieval rights after cancellation.
Lever opportunity collection and mutation reference ↗
List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeleted · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
Portable opportunity records are documented; files, complete history and native setup require separate retrieval.
Lever opportunity collection and mutation reference ↗
List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeleted · 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
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
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).
Lever API authentication and opportunity operations ↗
Authentication; Pagination; Opportunities; Rate Limits; Webhooks · Checked 2026-10-16
Rights to custom logic -
-
Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded.
The reviewed API guides do not establish ownership, reusable export or independent execution rights for native workflow artifacts.
Lever API authentication and opportunity operations ↗
Authentication; Pagination; Opportunities; Rate Limits; Webhooks · 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
Lever approves partner integrations and issues production OAuth credentials after review. Basic-auth customer keys are for internal workflows.
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
The authenticated API lists opportunity records as JSON. Public job postings are a separate feed. Follow opaque next/offset tokens; list pages contain at most 100 records. Opportunity filters include update-time ranges, stage and archive status.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Approved Lever partner OAuth application | OAuth 2.0 | Integration provider | Yes | partner agreement | 2026-10-16 |
| Customer internal-workflow API key | API key | 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
The opportunity API documents create and update operations; mutations require the corresponding granted scopes.
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
Use update-time polling and event hints. An update filter covers more changes than the returned updatedAt field. Opportunity update filters and candidateDeleted webhook identities support changed/deleted recruiting records; retain opportunity/contact identity mapping. Re-run opportunity pagination to rebuild permitted current records; webhook redelivery is bounded and does not recover erased payloads. Default per-key capacity is 10 requests/second, bursting to 20; defaults may vary. Use exponential backoff.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. Opportunity update filters and candidateDeleted webhook identities support changed/deleted recruiting records; retain opportunity/contact identity mapping. | Lever opportunity collection and mutation reference ↗List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeletedChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. Re-run opportunity pagination to rebuild permitted current records; webhook redelivery is bounded and does not recover erased payloads. | Lever opportunity collection and mutation reference ↗List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeletedChecked 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 opportunity records are documented; files, complete history and native setup require separate retrieval. 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 scopeLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. The authenticated API lists opportunity records as JSON. Public job postings are a separate feed. | Lever opportunity collection and mutation reference ↗List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeletedChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. Follow opaque next/offset tokens; list pages contain at most 100 records. | Lever opportunity collection and mutation reference ↗List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeletedChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. Opportunity filters include update-time ranges, stage and archive status. | Lever opportunity collection and mutation reference ↗List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeletedChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. Lever approves partner integrations and issues production OAuth credentials after review. Basic-auth customer keys are for internal workflows. | Lever partner product integration process ↗Steps 1–4; Basic Auth for customer internal workflows; production OAuth credentials; customer feature requirementsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. The reviewed API documentation establishes a technical route; lowest-paid-plan entitlement, partner charges and fixed API access fees remain unresolved. | Lever API authentication and opportunity operations ↗Authentication; Pagination; Opportunities; Rate Limits; WebhooksChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. The authentication and operation guides do not establish applicable processing, AI-use or redistribution rights. | Lever API authentication and opportunity operations ↗Authentication; Pagination; Opportunities; Rate Limits; WebhooksChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. The opportunity API documents create and update operations; mutations require the corresponding granted scopes. | Lever opportunity collection and mutation reference ↗List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeletedChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. A chosen provider integration must complete the disclosed approval route before customer authorization. | Lever partner product integration process ↗Steps 1–4; Basic Auth for customer internal workflows; production OAuth credentials; customer feature requirementsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. Use update-time polling and event hints. An update filter covers more changes than the returned updatedAt field. | Lever opportunity collection and mutation reference ↗List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeletedChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. Default per-key capacity is 10 requests/second, bursting to 20; defaults may vary. Use exponential backoff. | Lever API authentication and opportunity operations ↗Authentication; Pagination; Opportunities; Rate Limits; WebhooksChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. Authorized opportunity JSON can be held by the customer. | Lever opportunity collection and mutation reference ↗List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeletedChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. Current API retrieval does not establish contractual retrieval rights after cancellation. | Lever opportunity collection and mutation reference ↗List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeletedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. 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). | Lever API authentication and opportunity operations ↗Authentication; Pagination; Opportunities; Rate Limits; WebhooksChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Lever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. The reviewed API guides do not establish ownership, reusable export or independent execution rights for native workflow artifacts. | Lever API authentication and opportunity operations ↗Authentication; Pagination; Opportunities; Rate Limits; WebhooksChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedLever recruiting / opportunities and their documented profiles through approved partner OAuth; customer API keys are a separate internal-workflow route. Requisitions and complete account reconstruction are excluded. Portable opportunity records are documented; files, complete history and native setup require separate retrieval. | Lever opportunity collection and mutation reference ↗List all opportunities; updated_at_start/end; pagination; create/update opportunity; webhook candidateDeletedChecked 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.