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
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
The current API returns structured accounting entries within chosen scopes and filters.
Fetch accounting entries based on filters ↗
POST /v1/accounting-entries:search; Body; Response · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
Accounting-entry search exposes before/after pagination, hasNextPage and endCursor; pages contain 1–100 entries.
Fetch accounting entries based on filters ↗
Query Parameters > after; before; limit; Response > pagination · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
Structured accounting-entry filters are documented, without implying SQL or unlimited history.
Fetch accounting entries based on filters ↗
Body > includeDeleted; bookkeepingDateStart; bookkeepingDateEnd; employeeIds; accountIds · Checked 2026-10-16
Access cost barrier -
-
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
The lowest eligible paid plan and route-specific fixed API charges have not been established.
Standalone API Keys Overview ↗
Standalone API Keys Overview; Concepts and Terminology · 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
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
Standalone keys include preapproved single-company integrations; multi-customer production uses a separate OAuth route whose program criteria remain unresolved.
Standalone API Keys Overview ↗
Standalone API Keys Overview · Checked 2026-10-16
Downstream permission -
-
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
Standalone API Keys Overview ↗
Standalone API Keys Overview; Concepts and Terminology · 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
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
Create and update chart-of-accounts records; linked records can only be archived rather than deleted.
Chart of Accounts API Overview ↗
Account Management · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
Customer internal tools are supported; selected third-party single-company integrations require preapproval.
Standalone API Keys Overview ↗
Standalone API Keys Overview · 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
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
Export-job status webhooks support workflow refresh, not a complete accounting-entry change log.
Export API Overview ↗
Webhook Notifications for Status Change in Export Workflow · Checked 2026-10-16
Limit visibility 7.5/10
Numeric usage or polling guidance
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
The current Chart of Accounts overview states 600 requests per minute; broader quotas and reset behavior are not inferred.
Chart of Accounts API Overview ↗
Rate Limits · Checked 2026-10-16
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
Repeat selected accounting-entry search for reconciliation. includeDeleted is a filter, but a complete retained update/deletion identity contract remains unverified.
Fetch accounting entries based on filters ↗
Body > includeDeleted; Response · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
Repeat the same permitted accounting selection and all pages for current-state rebuilding. Deleted payload retention and historical event replay remain unestablished.
Fetch accounting entries based on filters ↗
Query Parameters; Response > pagination.hasNextPage; endCursor · 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
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
Structured export items can be transmitted to an external ERP/accounting system.
Export API Overview ↗
Overview; What are Export Jobs? · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
A customer cancellation retrieval window and any exit charges have not been established.
Standalone API Keys Overview ↗
Standalone API Keys Overview; Concepts and Terminology · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
Portable selected accounting records are established; receipt bytes, complete history and native configuration need separate evidence.
Fetch accounting entries based on filters ↗
Response; accounting entries · 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
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
External bookkeeping code can consume export items; native workflow definition portability remains unestablished.
Export API Overview ↗
Overview · Checked 2026-10-16
Rights to custom logic -
-
Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded.
Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Standalone API Keys Overview ↗
Standalone API Keys Overview; Concepts and Terminology · 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
Company-controlled standalone keys are generated in the Pleo web app and carry selected API scopes for one organization. They are intended for exploration, internal tooling and preapproved single-company integrations; OAuth is recommended for most production integrations, especially multiple customers. Standalone keys are available on request through CSM or Support, and production use requires Pleo approval.
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
POST /v1/accounting-entries:search returns accounting records with filters including bookkeeping dates, employees, accounts and includeDeleted. Current APIs use cursor or offset pagination; the accounting-entry and export-job scopes are distinct from a blanket expense-history export.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Pleo customer API | API key | Customer | 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
The current Chart of Accounts API documents create and update operations. Linked accounts cannot be deleted and can instead be archived; accounting export jobs may lock entries and alter expense status, so extraction workflows must distinguish passive reads from stateful export actions.
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
Selected accounting records can be re-queried and paginated for current-state reconciliation. Export-job status webhooks signal workflow progress; they do not establish complete accounting-record deltas, and includeDeleted alone does not establish retained tombstones with a universal update cursor.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. Repeat selected accounting-entry search for reconciliation. includeDeleted is a filter, but a complete retained update/deletion identity contract remains unverified. | Fetch accounting entries based on filters ↗Body > includeDeleted; ResponseChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. Repeat the same permitted accounting selection and all pages for current-state rebuilding. Deleted payload retention and historical event replay remain unestablished. | Fetch accounting entries based on filters ↗Query Parameters; Response > pagination.hasNextPage; endCursorChecked 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
Structured accounting entries and export items can be held in an external accounting system. Export selection and receipt retrieval limit the result; a data copy does not establish portable native approval logic or a complete Pleo configuration restore.
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 external bookkeeping integrations and reference-data mapping (while Pleo enforces scopes and export workflow state). Native workflow ownership, reusable export and independent execution remain unestablished.
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 scopeCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. The current API returns structured accounting entries within chosen scopes and filters. | Fetch accounting entries based on filters ↗POST /v1/accounting-entries:search; Body; ResponseChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. Accounting-entry search exposes before/after pagination, hasNextPage and endCursor; pages contain 1–100 entries. | Fetch accounting entries based on filters ↗Query Parameters > after; before; limit; Response > paginationChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. Structured accounting-entry filters are documented, without implying SQL or unlimited history. | Fetch accounting entries based on filters ↗Body > includeDeleted; bookkeepingDateStart; bookkeepingDateEnd; employeeIds; accountIdsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. Standalone keys include preapproved single-company integrations; multi-customer production uses a separate OAuth route whose program criteria remain unresolved. | Standalone API Keys Overview ↗Standalone API Keys OverviewChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. The lowest eligible paid plan and route-specific fixed API charges have not been established. | Standalone API Keys Overview ↗Standalone API Keys Overview; Concepts and TerminologyChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation. | Standalone API Keys Overview ↗Standalone API Keys Overview; Concepts and TerminologyChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. Create and update chart-of-accounts records; linked records can only be archived rather than deleted. | Chart of Accounts API Overview ↗Account ManagementChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. Customer internal tools are supported; selected third-party single-company integrations require preapproval. | Standalone API Keys Overview ↗Standalone API Keys OverviewChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. Export-job status webhooks support workflow refresh, not a complete accounting-entry change log. | Export API Overview ↗Webhook Notifications for Status Change in Export WorkflowChecked 2026-10-16 |
| How are integration limits disclosed? | Numeric usage or polling guidanceCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. The current Chart of Accounts overview states 600 requests per minute; broader quotas and reset behavior are not inferred. | Chart of Accounts API Overview ↗Rate LimitsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. Structured export items can be transmitted to an external ERP/accounting system. | Export API Overview ↗Overview; What are Export Jobs?Checked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. A customer cancellation retrieval window and any exit charges have not been established. | Standalone API Keys Overview ↗Standalone API Keys Overview; Concepts and TerminologyChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. External bookkeeping code can consume export items; native workflow definition portability remains unestablished. | Export API Overview ↗OverviewChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Current Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. Ownership, reusable export and independent execution of native workflow definitions remain unresolved. | Standalone API Keys Overview ↗Standalone API Keys Overview; Concepts and TerminologyChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedCurrent Pleo accounting-entry search/export APIs and chart-of-accounts create/update; company standalone keys and partner OAuth differ, while deprecated legacy APIs are excluded. Portable selected accounting records are established; receipt bytes, complete history and native configuration need separate evidence. | Fetch accounting entries based on filters ↗Response; accounting entriesChecked 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.