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
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
The payable snapshot API returns structured operational accounting records.
Retrieving Spend Data ↗
Retrieving Spend Data; result.data · Checked 2026-10-16
Bulk delivery 10.0/10
Customer-initiated native snapshot or full scoped table export
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Customers request a native asynchronous snapshot of the selected payable scope and traverse all result pages.
Retrieving Spend Data ↗
Retrieving Spend Data; Request a snapshot; Get a snapshot · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Structured status, export-date, updatedFrom and sorting selection are documented.
Retrieving Spend Data ↗
Request snapshot example; updatedFrom; bookkeepingStatus · Checked 2026-10-16
Access cost barrier -
-
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
The lowest eligible paid plan and route-specific fixed API charges have not been established.
Getting access ↗
Which access do you need?; Create an API key; Access to experimental features · 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
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Multi-customer OAuth apps are set up through the partnerships team; customer approval is an additional step.
Getting access ↗
Which access do you need? > Build an integration used by many Spendesk customers · Checked 2026-10-16
Downstream permission -
-
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
Getting access ↗
Which access do you need?; Create an API key; Access to experimental features · 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
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Named accounting-field changes require Controller role, experimental scope and optimistic locking.
Update Payable accounting fields ↗
Update Payable accounting fields; Allowed Scopes; OpenAPI paths./v1/payables/{id}.patch · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Company-owned reporting and ERP integrations use customer credentials; partner distribution and experimental scopes are separate.
Getting access ↗
Which access do you need? > Connect your own tools · 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
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Overlapping daily updatedFrom snapshots support payable refresh; webhooks are optional experimental hints.
Retrieving Spend Data ↗
Daily retrieval recommendation > updatedFrom · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Company/credential limits, concurrency limits, response headers and 429 reset handling are published.
Rate Limiting ↗
Limits; HTTP Headers · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Changed payables can be selected; complete hard-delete identity coverage is unestablished.
Retrieving Spend Data ↗
Daily retrieval recommendation > updatedFrom · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Retries occur immediately, every ten minutes for one hour, then every two hours for three days. Fresh payable snapshots provide separate current-state recovery; cached files are not historical event replay.
Using webhooks (experimental) ↗
Delivery retry schedule; supported events · 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
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Structured snapshot records can be retained externally before cache expiry.
Retrieving Spend Data ↗
Get a snapshot; result.data; ten-hour cache · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
A customer cancellation retrieval window and any exit charges have not been established.
Getting access ↗
Which access do you need?; Create an API key; Access to experimental features · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Portable selected payables and accounting fields are established; attachments and complete native configuration are separate.
Retrieving Spend Data ↗
Retrieving Spend Data; result.data · 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
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Customer scripts, BI and ERP sync integrations are supported; native definition ownership remains unestablished.
Getting access ↗
Which access do you need? > Connect your own tools · Checked 2026-10-16
Rights to custom logic -
-
Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions.
Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Getting access ↗
Which access do you need?; Create an API key; Access to experimental features · 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
An Account Owner or Admin creates company API credentials with selected scopes. Organization keys and partner OAuth have separate setup paths; experimental endpoints and webhooks require an access request, and a token cannot exceed the scopes assigned to its key.
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
Request a payable snapshot, poll until COMPLETE and traverse result pages during its ten-hour cache window. Selection includes bookkeeping status and updatedFrom; identical active requests return the same key, and overlapping open snapshots can produce 409 conflicts.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Spendesk customer API | OAuth client credentials | Customer | Not confirmed | Customer-supplied credentials | 2026-10-16 |
| Spendesk partner OAuth application | OAuth 2.0 | Integration provider | Yes | Partner approval | 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 lowest eligible customer plan and any fixed API, partner or setup charges remain unestablished. Payment-processing charges do not by themselves establish an API-access surcharge.
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
PATCH /v1/payables/{id} changes accounting fields under experimental:accounting:update and a Controller role. It uses optimistic locking; replacing lineItems is a full replacement and recalculates tax from the supplied tax account, so changes need exact field and accounting-policy 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
Daily overlapping updatedFrom snapshots support refresh, with optional experimental webhooks for payable-created/prepared and settlement-created events. Delivery retries extend over three days; these notifications do not cover every update or deletion, and the snapshot cache is not an event-retention window.
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 establishedSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Changed payables can be selected; complete hard-delete identity coverage is unestablished. | Retrieving Spend Data ↗Daily retrieval recommendation > updatedFromChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Retries occur immediately, every ten minutes for one hour, then every two hours for three days. Fresh payable snapshots provide separate current-state recovery; cached files are not historical event replay. | Using webhooks (experimental) ↗Delivery retry schedule; supported eventsChecked 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
The caller can retain structured payable snapshots and selected receipts through separate attachment access. Cached snapshots expire, so download all pages promptly and retain the independent copy; whole-account configuration and native approval artifacts are unestablished.
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 write external reporting and accounting integrations (with company and scope checks at the API boundary). Native workflow definition ownership and independent execution remain unresolved.
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 scopeSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. The payable snapshot API returns structured operational accounting records. | Retrieving Spend Data ↗Retrieving Spend Data; result.dataChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Customer-initiated native snapshot or full scoped table exportSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Customers request a native asynchronous snapshot of the selected payable scope and traverse all result pages. | Retrieving Spend Data ↗Retrieving Spend Data; Request a snapshot; Get a snapshotChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Structured status, export-date, updatedFrom and sorting selection are documented. | Retrieving Spend Data ↗Request snapshot example; updatedFrom; bookkeepingStatusChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Multi-customer OAuth apps are set up through the partnerships team; customer approval is an additional step. | Getting access ↗Which access do you need? > Build an integration used by many Spendesk customersChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. The lowest eligible paid plan and route-specific fixed API charges have not been established. | Getting access ↗Which access do you need?; Create an API key; Access to experimental featuresChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation. | Getting access ↗Which access do you need?; Create an API key; Access to experimental featuresChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Named accounting-field changes require Controller role, experimental scope and optimistic locking. | Update Payable accounting fields ↗Update Payable accounting fields; Allowed Scopes; OpenAPI paths./v1/payables/{id}.patchChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Company-owned reporting and ERP integrations use customer credentials; partner distribution and experimental scopes are separate. | Getting access ↗Which access do you need? > Connect your own toolsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Overlapping daily updatedFrom snapshots support payable refresh; webhooks are optional experimental hints. | Retrieving Spend Data ↗Daily retrieval recommendation > updatedFromChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Company/credential limits, concurrency limits, response headers and 429 reset handling are published. | Rate Limiting ↗Limits; HTTP HeadersChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Structured snapshot records can be retained externally before cache expiry. | Retrieving Spend Data ↗Get a snapshot; result.data; ten-hour cacheChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. A customer cancellation retrieval window and any exit charges have not been established. | Getting access ↗Which access do you need?; Create an API key; Access to experimental featuresChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Customer scripts, BI and ERP sync integrations are supported; native definition ownership remains unestablished. | Getting access ↗Which access do you need? > Connect your own toolsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Spendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Ownership, reusable export and independent execution of native workflow definitions remain unresolved. | Getting access ↗Which access do you need?; Create an API key; Access to experimental featuresChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedSpendesk company-scoped payable snapshots and wallet reads, with optional experimental payable accounting-field PATCH/webhooks; partner OAuth and organization-level grants are separate conditions. Portable selected payables and accounting fields are established; attachments and complete native configuration are separate. | Retrieving Spend Data ↗Retrieving Spend Data; result.dataChecked 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
- The lowest eligible paid plan and route-specific fixed API charges have not been established.
- Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
- A customer cancellation retrieval window and any exit charges have not been established.
- Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.