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
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
Authorized REST resources return JSON records.
Reapit Foundations REST contract ↗
Retrieving data · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
pageSize/pageNumber traverse authorized top-level collections.
Reapit Foundations REST contract ↗
Retrieving data · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
Endpoint query parameters provide structured resource filtering.
Reapit Foundations REST contract ↗
Retrieving data; boolean query parameters · Checked 2026-10-16
Access cost barrier -
-
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges.
Reapit Foundations REST contract ↗
Reviewed product documentation; stated limitation not resolved · 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
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
App approval and customer installation apply even to an agency’s own private app.
Reapit customer-data installation requirements ↗
Accessing your own data; private listing · Checked 2026-10-16
Downstream permission -
-
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
The reviewed technical documentation does not establish contractual permission for the declared downstream processing.
Reapit Foundations REST contract ↗
Reviewed product documentation; stated limitation not resolved · 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
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
POST /documents creates a named document from a supplied file URL.
Reapit Foundations REST contract ↗
Uploading files; POST /documents example · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
Approved apps use fixed APIs after customer installation.
Reapit Foundations REST contract ↗
Registering your app; Customer installation · 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
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
Resource webhooks notify scoped changes.
Reapit webhook contract ↗
Subscription topics · Checked 2026-10-16
Limit visibility 7.5/10
Numeric usage or polling guidance
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
Numeric request/concurrency/daily limits are published with 429 behavior.
Reapit Foundations REST contract ↗
Rate limits · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
Created/modified topics are explicit; null-new deletion/archive payloads do not establish a universal delete-topic guarantee.
Reapit webhook contract ↗
Subscription topics; Payload schema · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
Six total delivery attempts for eligible failures; no retained consumer replay established.
Reapit webhook contract ↗
Failure handling and exponential backoff · 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
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
Authorized JSON resource records can be held externally.
Reapit Foundations REST contract ↗
Retrieving data · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
No retrieval window or export charge at cancellation is established by these technical sources.
Reapit Foundations REST contract ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
Portable scoped API records, without proof of whole-agency history/configuration.
Reapit Foundations REST contract ↗
Retrieving 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
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
Registered external apps integrate with customer-granted resources.
Reapit Foundations REST contract ↗
Registering your app; Customer installation · Checked 2026-10-16
Rights to custom logic -
-
Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate.
Rights to native workflow artifacts and independent execution are not established.
Reapit Foundations REST contract ↗
Reviewed product documentation; stated limitation not resolved · 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
The developer’s app receives a client ID/secret. Client credentials or user authorization obtain scoped tokens, and the customer must install the app; customer database identity accompanies machine-to-machine requests.
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
Top-level REST collections use pageNumber/pageSize, default 25 and maximum 100 unless an endpoint says otherwise. Resource filters and selected scopes determine the visible data.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Approved customer-installed client-credentials app | OAuth client credentials | Integration provider | Yes | approved public/private listing; customer installation/scopes; app client id/secret and reapit-customer header | 2026-10-16 |
| Approved customer-installed authorization-code app | OAuth 2.0 | Integration provider | Yes | approved listing, customer installation and reapit connect user 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
Fixed API charges, minimum customer package and applicable currency were not established. Webhook deliveries count toward developer billing; the API documents 20 requests/second, five concurrent per customer and 250,000/day.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
POST /documents creates a document after upload, with validation. Updates use PATCH with an exact If-Match ETag and reject concurrent edits with 412; a particular document-update schema was not verified.
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
Scoped webhooks include created/modified topics and identity; payloads represent deletion/archive with a null new object where applicable. Delivery retries five times after the initial attempt, excludes 4xx and sandbox failures, and does not guarantee ordering.
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 establishedReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. Created/modified topics are explicit; null-new deletion/archive payloads do not establish a universal delete-topic guarantee. | Reapit webhook contract ↗Subscription topics; Payload schemaChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. Six total delivery attempts for eligible failures; no retained consumer replay established. | Reapit webhook contract ↗Failure handling and exponential backoffChecked 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
Authorized collection JSON supports portable records. The API does not establish a whole-agency database restore or all historical documents (native artifacts and cancellation retrieval remain unverified).
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
Approved applications implement external business rules over fixed APIs. Client code ownership and independent rights to native Reapit workflow definitions were not established.
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 scopeReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. Authorized REST resources return JSON records. | Reapit Foundations REST contract ↗Retrieving dataChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. pageSize/pageNumber traverse authorized top-level collections. | Reapit Foundations REST contract ↗Retrieving dataChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. Endpoint query parameters provide structured resource filtering. | Reapit Foundations REST contract ↗Retrieving data; boolean query parametersChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. App approval and customer installation apply even to an agency’s own private app. | Reapit customer-data installation requirements ↗Accessing your own data; private listingChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges. | Reapit Foundations REST contract ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. The reviewed technical documentation does not establish contractual permission for the declared downstream processing. | Reapit Foundations REST contract ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. POST /documents creates a named document from a supplied file URL. | Reapit Foundations REST contract ↗Uploading files; POST /documents exampleChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. Approved apps use fixed APIs after customer installation. | Reapit Foundations REST contract ↗Registering your app; Customer installationChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. Resource webhooks notify scoped changes. | Reapit webhook contract ↗Subscription topicsChecked 2026-10-16 |
| How are integration limits disclosed? | Numeric usage or polling guidanceReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. Numeric request/concurrency/daily limits are published with 429 behavior. | Reapit Foundations REST contract ↗Rate limitsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. Authorized JSON resource records can be held externally. | Reapit Foundations REST contract ↗Retrieving dataChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. No retrieval window or export charge at cancellation is established by these technical sources. | Reapit Foundations REST contract ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. Registered external apps integrate with customer-granted resources. | Reapit Foundations REST contract ↗Registering your app; Customer installationChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Reapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. Rights to native workflow artifacts and independent execution are not established. | Reapit Foundations REST contract ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedReapit Foundations approved apps with customer installation, contact/resource REST reads, document creation and scoped webhooks; Reapit Agent database and other product access are separate. Portable scoped API records, without proof of whole-agency history/configuration. | Reapit Foundations REST contract ↗Retrieving 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
- Lowest-plan API entitlement and fixed access fees
- Complete attachments/history and deletion recovery
- Native workflow rights and cancellation retrieval
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.