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
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
REST v1 work-order objects are structured JSON.
MaintainX work-order OpenAPI contract ↗
GET /workorders · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
Work-order cursor pagination supports collection traversal.
MaintainX timestamp polling and pagination ↗
Pagination · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
updatedAt[gte] and endpoint filters are documented.
MaintainX timestamp polling and pagination ↗
Basic Pattern · Checked 2026-10-16
Access cost barrier -
-
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges.
MaintainX work-order OpenAPI 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 -
-
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
The reviewed MaintainX scope does not establish third-party eligibility.
MaintainX work-order OpenAPI contract ↗
Reviewed product documentation; stated limitation not resolved · Checked 2026-10-16
Downstream permission -
-
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
The reviewed technical documentation does not establish contractual permission for the declared downstream processing.
MaintainX work-order OpenAPI 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 7.5/10
Create and update in one business domain
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
OpenAPI documents work-order POST creation and PATCH update.
MaintainX work-order OpenAPI contract ↗
POST /workorders; PATCH /workorders/{id} · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
Customers generate keys and use fixed REST endpoints from their API clients.
MaintainX REST key generation and organization scope ↗
Generate a MaintainX API Key; Test Your API Requests · 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
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
Timestamp filters and webhook hints support change extraction.
MaintainX timestamp polling and pagination ↗
Basic Pattern · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
User/org numeric budgets, remaining/reset headers and 429 recovery are published.
MaintainX rate budgets and reset headers ↗
Default Rate Limits; Rate Limit Headers · Checked 2026-10-16
CDC and deletion capture 5.0/10
Updates identified; deletion capture not established
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
updatedAt polls identify updates; hard-delete capture is unverified.
MaintainX timestamp polling and pagination ↗
Basic Pattern · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
Overlapping timestamp queries recover currently retained record changes, without durable event history.
MaintainX timestamp polling and pagination ↗
Basic Pattern; Pagination · 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
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
Authorized REST responses supply work-order record copies.
MaintainX work-order OpenAPI contract ↗
GET /workorders response · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
No retrieval window or export charge at cancellation is established by these technical sources.
MaintainX work-order OpenAPI 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
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
Portable work-order JSON; no proof of complete history/files/native definitions.
MaintainX work-order OpenAPI contract ↗
GET /workorders response · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 5.0/10
Customer-editable native workflows or agent configurations
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
Premium offers meter-triggered work-order automation; Enterprise expands custom conditions/actions.
MaintainX native automation plan scope ↗
Plan Type; feature differences · Checked 2026-10-16
Rights to custom logic -
-
MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate.
Rights to native workflow artifacts and independent execution are not established.
MaintainX work-order OpenAPI 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
Customers create a key under Organization Settings > Integrations > API Keys. A multi-organization option depends on plan entitlement and explicit selection; multi-org requests identify target organizations.
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 published OpenAPI contract includes work-order enumeration and POST/PATCH operations. updatedAt filters must remain identical across pages; offset-based streams can shift during extraction.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer organization REST API key | API key | Customer | Not confirmed | customer generates bearer key; single-org default; multi-org plan/option plus organization headers | 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 default limits are 100 requests/minute per user and 500/minute per organization, with reset headers. The reviewed REST setup guide does not establish a minimum plan or fixed API fee; separate Reporting/Zapier entitlements are not copied to REST.
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 /workorders creates and PATCH /workorders/{id} updates a work order. Required schemas and organization scope apply; external ID uniqueness can help reconciliation but is not a universal idempotency guarantee.
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
Timestamp polling overlaps and deduplicates by ID. Webhooks are signed and time out after 10 seconds; prolonged failures can delete a subscription, with no verified retained replay 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 establishedMaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. updatedAt polls identify updates; hard-delete capture is unverified. | MaintainX timestamp polling and pagination ↗Basic PatternChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointMaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. Overlapping timestamp queries recover currently retained record changes, without durable event history. | MaintainX timestamp polling and pagination ↗Basic Pattern; PaginationChecked 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
Current authorized work-order records can be rebuilt through collection traversal. Full historical versions, hard-deleted payloads and all attachments 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
MaintainX supports native workflow automations on named plans and external integrations through fixed APIs. Artifact rights and independent execution were not established (external identifiers do not preserve workflow definitions).
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 scopeMaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. REST v1 work-order objects are structured JSON. | MaintainX work-order OpenAPI contract ↗GET /workordersChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsMaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. Work-order cursor pagination supports collection traversal. | MaintainX timestamp polling and pagination ↗PaginationChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersMaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. updatedAt[gte] and endpoint filters are documented. | MaintainX timestamp polling and pagination ↗Basic PatternChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. The reviewed MaintainX scope does not establish third-party eligibility. | MaintainX work-order OpenAPI contract ↗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? | -MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. The reviewed documentation does not establish lowest-plan entitlement and access-specific fixed charges. | MaintainX work-order OpenAPI contract ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. The reviewed technical documentation does not establish contractual permission for the declared downstream processing. | MaintainX work-order OpenAPI contract ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainMaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. OpenAPI documents work-order POST creation and PATCH update. | MaintainX work-order OpenAPI contract ↗POST /workorders; PATCH /workorders/{id}Checked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionMaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. Customers generate keys and use fixed REST endpoints from their API clients. | MaintainX REST key generation and organization scope ↗Generate a MaintainX API Key; Test Your API RequestsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksMaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. Timestamp filters and webhook hints support change extraction. | MaintainX timestamp polling and pagination ↗Basic PatternChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsMaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. User/org numeric budgets, remaining/reset headers and 429 recovery are published. | MaintainX rate budgets and reset headers ↗Default Rate Limits; Rate Limit HeadersChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsMaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. Authorized REST responses supply work-order record copies. | MaintainX work-order OpenAPI contract ↗GET /workorders responseChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. No retrieval window or export charge at cancellation is established by these technical sources. | MaintainX work-order OpenAPI contract ↗Reviewed product documentation; stated limitation not resolvedChecked 2026-10-16 |
| How can customers define their own business logic? | Customer-editable native workflows or agent configurationsMaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. Premium offers meter-triggered work-order automation; Enterprise expands custom conditions/actions. | MaintainX native automation plan scope ↗Plan Type; feature differencesChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -MaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. Rights to native workflow artifacts and independent execution are not established. | MaintainX work-order OpenAPI 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 unverifiedMaintainX REST v1 work-order list/create/update and customer bearer API keys; timestamp polling and signed webhook hints; Reporting API and OT integrations are separate. Portable work-order JSON; no proof of complete history/files/native definitions. | MaintainX work-order OpenAPI contract ↗GET /workorders responseChecked 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.