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
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
Published reference documents asset/inspection/report list methods; active production support remains uncertain.
HappyCo published API 2.8.0 reference ↗
Version 2.8.0; AssetService; InspectionService; ReportService · Checked 2026-10-16
Bulk delivery -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
The reviewed HappyCo scope does not establish bulk delivery.
HappyCo published API 2.8.0 reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Query expressiveness -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
The reviewed HappyCo scope does not establish query expressiveness.
HappyCo published API 2.8.0 reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Access cost barrier -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges.
HappyCo published API 2.8.0 reference ↗
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 -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
The reviewed HappyCo scope does not establish third-party eligibility.
HappyCo published API 2.8.0 reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Downstream permission -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
The reviewed technical documentation does not establish contractual permission for the declared downstream processing.
HappyCo published API 2.8.0 reference ↗
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 7.5/10
Create and update in one business domain
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
AssetService includes CreateAssets and UpdateAssets methods; active auth/permission contract unresolved.
HappyCo published API 2.8.0 reference ↗
assetServiceCreateAssets; assetServiceUpdateAssets · Checked 2026-10-16
Custom application path -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
The reviewed HappyCo scope does not establish custom application path.
HappyCo published API 2.8.0 reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
The reviewed HappyCo scope does not establish refresh mechanism.
HappyCo published API 2.8.0 reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Limit visibility -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
A numeric quota and recovery contract are not established by the reviewed route documentation.
HappyCo published API 2.8.0 reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
CDC and deletion capture -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
The reviewed HappyCo scope does not establish cdc and deletion capture.
HappyCo published API 2.8.0 reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Replay and gap recovery -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
No supported recovery mechanism or retention contract is established for the declared route.
HappyCo published API 2.8.0 reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
The reviewed HappyCo scope does not establish export custody.
HappyCo published API 2.8.0 reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
No retrieval window or export charge at cancellation is established by these technical sources.
HappyCo published API 2.8.0 reference ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Planned migration fidelity -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
The reviewed HappyCo scope does not establish planned migration fidelity.
HappyCo published API 2.8.0 reference ↗
Reviewed product documentation; stated limitation not resolved · 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
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
The published reference includes external client SDK examples for asset methods.
HappyCo published API 2.8.0 reference ↗
AssetService Usage and SDK Samples · Checked 2026-10-16
Rights to custom logic -
-
Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context.
Rights to native workflow artifacts and independent execution are not established.
HappyCo published API 2.8.0 reference ↗
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 public reference contains SDK/curl samples for asset operations without an established credential contract. An undated overview directs vendors to contact HappyCo for account provisioning; that does not establish the gate for every data API.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
The 2.8.0 reference lists asset, inspection and report methods at v1 paths. Pagination, schema completeness and current version support were not verified; no whole-account bulk claim is made.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Published asset API, credential contract unresolved | Not confirmed | Customer | Not confirmed | customer is a planning custody target only; credential issuer/holder, supported version and production eligibility remain unverified | 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
Minimum package, fixed API charges, customer versus partner credentials and numeric limits remain unresolved. Public documentation availability does not establish self-service production access.
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
Asset create and update operations are documented in the public reference. Authentication, operation permissions, retry safety and active tenant support must be verified before execution.
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
An undated overview describes gRPC streaming and retained pending events, but gives no current supported retention contract. The review does not credit that description as durable replay.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. The reviewed HappyCo scope does not establish cdc and deletion capture. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. No supported recovery mechanism or retention contract is established for the declared route. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 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
Documented asset/inspection list methods provide a technical record interface. A verified current permitted export, full attachments/history and independent restore were not established.
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
The public SDK examples support external client code as a documented technical path. Native workflow authoring rights and cancellation retrieval remain unknown (account-provisioning access is a separate interface).
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 scopePublic HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. Published reference documents asset/inspection/report list methods; active production support remains uncertain. | HappyCo published API 2.8.0 reference ↗Version 2.8.0; AssetService; InspectionService; ReportServiceChecked 2026-10-16 |
| How can customers retrieve data in bulk? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. The reviewed HappyCo scope does not establish bulk delivery. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. The reviewed HappyCo scope does not establish query expressiveness. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. The reviewed HappyCo scope does not establish third-party eligibility. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. The reviewed technical documentation does not establish contractual permission for the declared downstream processing. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainPublic HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. AssetService includes CreateAssets and UpdateAssets methods; active auth/permission contract unresolved. | HappyCo published API 2.8.0 reference ↗assetServiceCreateAssets; assetServiceUpdateAssetsChecked 2026-10-16 |
| How can customers connect an application they build or choose? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. The reviewed HappyCo scope does not establish custom application path. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. The reviewed HappyCo scope does not establish refresh mechanism. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| How are integration limits disclosed? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. A numeric quota and recovery contract are not established by the reviewed route documentation. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Where can a usable data copy be delivered? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. The reviewed HappyCo scope does not establish export custody. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. No retrieval window or export charge at cancellation is established by these technical sources. | HappyCo published API 2.8.0 reference ↗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 establishedPublic HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. The published reference includes external client SDK examples for asset methods. | HappyCo published API 2.8.0 reference ↗AssetService Usage and SDK SamplesChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. Rights to native workflow artifacts and independent execution are not established. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | -Public HappyCo API 2.8.0 reference for v1 asset/inspection/report methods; active production authentication, version support and eligibility are unverified. Undated gRPC overview is separate context. The reviewed HappyCo scope does not establish planned migration fidelity. | HappyCo published API 2.8.0 reference ↗Reviewed product documentation; stated limitation not resolvedChecked 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
- Active supported API version and authentication contract
- Customer versus vendor credential custody and approval gate
- Pagination, numeric quotas and permitted export fidelity
- Current event retention, deletion coverage and native workflow rights
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.