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
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
candidate.list provides permitted candidate profiles; confidential jobs/projects and private fields require explicit additional permissions.
Ashby candidate list ↗
candidate.list: candidatesRead; cursor/limit; syncToken; createdAfter/Before · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
A full sync traverses nextCursor until moreDataAvailable is false; candidate pages allow up to 100 results.
Ashby candidate list ↗
candidate.list: candidatesRead; cursor/limit; syncToken; createdAfter/Before · Checked 2026-10-16
Ashby pagination and incremental synchronization ↗
Full sync; incremental sync; 100-page depth; 14-day cursor and sync-token expiry; full-sync recovery · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
Candidate lists filter creation ranges and accept incremental sync tokens; arbitrary cross-object SQL is not established.
Ashby candidate list ↗
candidate.list: candidatesRead; cursor/limit; syncToken; createdAfter/Before · Checked 2026-10-16
Access cost barrier -
-
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
The reviewed API documentation establishes a technical route; lowest-paid-plan entitlement, partner charges and fixed API access fees remain unresolved.
Ashby API authentication and permission model ↗
HTTP Basic API keys; candidatesRead/candidatesWrite; confidential jobs and private fields; Merge permission mapping · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
Organization Admins create and scope API keys for integrations; the authentication guide documents third-party Merge permissions without a separate provider gate for this key route.
Ashby API credential creation ↗
Organization Admin requirement; Admin > Integrations > API Keys · Checked 2026-10-16
Ashby API authentication and permission model ↗
HTTP Basic API keys; candidatesRead/candidatesWrite; confidential jobs and private fields; Merge permission mapping · Checked 2026-10-16
Downstream permission -
-
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
The authentication and operation guides do not establish applicable processing, AI-use or redistribution rights.
Ashby API authentication and permission model ↗
HTTP Basic API keys; candidatesRead/candidatesWrite; confidential jobs and private fields; Merge permission mapping · 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
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
candidate.create and candidate.update create and change recruiting profiles under candidatesWrite. Additional operations and external effects need separate approval.
Ashby create candidate ↗
candidate.create: candidatesWrite; candidate fields · Checked 2026-10-16
Ashby update candidate ↗
candidate.update: candidateId and writable fields; candidatesWrite · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
Customers can build or choose a client using the documented customer credential route.
Ashby API credential creation ↗
Organization Admin requirement; Admin > Integrations > API Keys · Checked 2026-10-16
Ashby API authentication and permission model ↗
HTTP Basic API keys; candidatesRead/candidatesWrite; confidential jobs and private fields; Merge permission mapping · 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
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
candidate.list accepts a prior syncToken and returns modified records; endpoints without that parameter require full refresh.
Ashby pagination and incremental synchronization ↗
Full sync; incremental sync; 100-page depth; 14-day cursor and sync-token expiry; full-sync recovery · Checked 2026-10-16
Limit visibility -
-
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
The reviewed candidate API sources establish page/depth limits, but no numeric general service quota or throttle recovery contract. MCP and report limits cannot substitute for this route.
Ashby API request conventions ↗
RPC-style POST requests; backend proxy recommendation · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
Candidate incremental sync identifies modified records. Tombstones or complete deleted-record identities are not established by this contract.
Ashby pagination and incremental synchronization ↗
Full sync; incremental sync; 100-page depth; 14-day cursor and sync-token expiry; full-sync recovery · Checked 2026-10-16
Replay and gap recovery 10.0/10
Consumer checkpoint with documented retention limits and resnapshot recovery
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
Store the new syncToken only after the final page commits. Cursors/tokens expire after 14 days; invalid/oversized syncs require a full restart without cursor or syncToken.
Ashby pagination and incremental synchronization ↗
Full sync; incremental sync; 100-page depth; 14-day cursor and sync-token expiry; full-sync recovery · 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
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
The API returns structured records that a permitted client can retain as a customer-held copy.
Ashby candidate list ↗
candidate.list: candidatesRead; cursor/limit; syncToken; createdAfter/Before · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
Current API retrieval does not establish contractual retrieval rights after cancellation.
Ashby candidate list ↗
candidate.list: candidatesRead; cursor/limit; syncToken; createdAfter/Before · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
Portable records cover the declared collection. Files, full activity history, workflow configuration and a whole-product restore remain outside the established scope.
Ashby candidate list ↗
candidate.list: candidatesRead; cursor/limit; syncToken; createdAfter/Before · 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
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
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).
Ashby API authentication and permission model ↗
HTTP Basic API keys; candidatesRead/candidatesWrite; confidential jobs and private fields; Merge permission mapping · Checked 2026-10-16
Rights to custom logic -
-
Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope.
The reviewed API guides do not establish ownership, reusable export or independent execution rights for native workflow artifacts.
Ashby API authentication and permission model ↗
HTTP Basic API keys; candidatesRead/candidatesWrite; confidential jobs and private fields; Merge permission mapping · 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
Organization Admins create and scope API keys for integrations; the authentication guide documents third-party Merge permissions without a separate provider gate for this key route.
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.list provides permitted candidate profiles; confidential jobs/projects and private fields require explicit additional permissions. A full sync traverses nextCursor until moreDataAvailable is false; candidate pages allow up to 100 results. Candidate lists filter creation ranges and accept incremental sync tokens; arbitrary cross-object SQL is not established.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Administrator-scoped candidate 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
candidate.create and candidate.update create and change recruiting profiles under candidatesWrite. Additional operations and external effects need separate approval.
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
candidate.list accepts a prior syncToken and returns modified records; endpoints without that parameter require full refresh. Candidate incremental sync identifies modified records. Tombstones or complete deleted-record identities are not established by this contract. Store the new syncToken only after the final page commits. Cursors/tokens expire after 14 days; invalid/oversized syncs require a full restart without cursor or syncToken. The reviewed candidate API sources establish page/depth limits, but no numeric general service quota or throttle recovery contract. MCP and report limits cannot substitute for this route.
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 establishedAshby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. Candidate incremental sync identifies modified records. Tombstones or complete deleted-record identities are not established by this contract. | Ashby pagination and incremental synchronization ↗Full sync; incremental sync; 100-page depth; 14-day cursor and sync-token expiry; full-sync recoveryChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Consumer checkpoint with documented retention limits and resnapshot recoveryAshby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. Store the new syncToken only after the final page commits. Cursors/tokens expire after 14 days; invalid/oversized syncs require a full restart without cursor or syncToken. | Ashby pagination and incremental synchronization ↗Full sync; incremental sync; 100-page depth; 14-day cursor and sync-token expiry; full-sync recoveryChecked 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 scopeAshby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. candidate.list provides permitted candidate profiles; confidential jobs/projects and private fields require explicit additional permissions. | Ashby candidate list ↗candidate.list: candidatesRead; cursor/limit; syncToken; createdAfter/BeforeChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsAshby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. A full sync traverses nextCursor until moreDataAvailable is false; candidate pages allow up to 100 results. | Ashby candidate list ↗candidate.list: candidatesRead; cursor/limit; syncToken; createdAfter/BeforeChecked 2026-10-16 Ashby pagination and incremental synchronization ↗Full sync; incremental sync; 100-page depth; 14-day cursor and sync-token expiry; full-sync recoveryChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersAshby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. Candidate lists filter creation ranges and accept incremental sync tokens; arbitrary cross-object SQL is not established. | Ashby candidate list ↗candidate.list: candidatesRead; cursor/limit; syncToken; createdAfter/BeforeChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalAshby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. Organization Admins create and scope API keys for integrations; the authentication guide documents third-party Merge permissions without a separate provider gate for this key route. | Ashby API credential creation ↗Organization Admin requirement; Admin > Integrations > API KeysChecked 2026-10-16 Ashby API authentication and permission model ↗HTTP Basic API keys; candidatesRead/candidatesWrite; confidential jobs and private fields; Merge permission mappingChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. The reviewed API documentation establishes a technical route; lowest-paid-plan entitlement, partner charges and fixed API access fees remain unresolved. | Ashby API authentication and permission model ↗HTTP Basic API keys; candidatesRead/candidatesWrite; confidential jobs and private fields; Merge permission mappingChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. The authentication and operation guides do not establish applicable processing, AI-use or redistribution rights. | Ashby API authentication and permission model ↗HTTP Basic API keys; candidatesRead/candidatesWrite; confidential jobs and private fields; Merge permission mappingChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainAshby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. candidate.create and candidate.update create and change recruiting profiles under candidatesWrite. Additional operations and external effects need separate approval. | Ashby create candidate ↗candidate.create: candidatesWrite; candidate fieldsChecked 2026-10-16 Ashby update candidate ↗candidate.update: candidateId and writable fields; candidatesWriteChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionAshby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. Customers can build or choose a client using the documented customer credential route. | Ashby API credential creation ↗Organization Admin requirement; Admin > Integrations > API KeysChecked 2026-10-16 Ashby API authentication and permission model ↗HTTP Basic API keys; candidatesRead/candidatesWrite; confidential jobs and private fields; Merge permission mappingChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksAshby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. candidate.list accepts a prior syncToken and returns modified records; endpoints without that parameter require full refresh. | Ashby pagination and incremental synchronization ↗Full sync; incremental sync; 100-page depth; 14-day cursor and sync-token expiry; full-sync recoveryChecked 2026-10-16 |
| How are integration limits disclosed? | -Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. The reviewed candidate API sources establish page/depth limits, but no numeric general service quota or throttle recovery contract. MCP and report limits cannot substitute for this route. | Ashby API request conventions ↗RPC-style POST requests; backend proxy recommendationChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsAshby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. The API returns structured records that a permitted client can retain as a customer-held copy. | Ashby candidate list ↗candidate.list: candidatesRead; cursor/limit; syncToken; createdAfter/BeforeChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. Current API retrieval does not establish contractual retrieval rights after cancellation. | Ashby candidate list ↗candidate.list: candidatesRead; cursor/limit; syncToken; createdAfter/BeforeChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedAshby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. 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). | Ashby API authentication and permission model ↗HTTP Basic API keys; candidatesRead/candidatesWrite; confidential jobs and private fields; Merge permission mappingChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Ashby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. The reviewed API guides do not establish ownership, reusable export or independent execution rights for native workflow artifacts. | Ashby API authentication and permission model ↗HTTP Basic API keys; candidatesRead/candidatesWrite; confidential jobs and private fields; Merge permission mappingChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedAshby / candidate profiles through administrator-managed API keys on API version 2026-01-01, including paginated full/incremental lists and candidate create/update. MCP, closed-beta audit APIs, reports and assessment partner execution are outside this scope. Portable records cover the declared collection. Files, full activity history, workflow configuration and a whole-product restore remain outside the established scope. | Ashby candidate list ↗candidate.list: candidatesRead; cursor/limit; syncToken; createdAfter/BeforeChecked 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
- Numeric service quota and throttle recovery contract
- 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.