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
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
Cards have structured fields and related-object endpoints.
Trello Cards REST API ↗
Get a Card · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
Board collections and before/since action paging permit iterative retrieval.
Trello API introduction ↗
Paging and Actions · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
Search queries select matching boards and cards.
Trello API introduction ↗
Search · Checked 2026-10-16
Access cost barrier -
-
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
Reviewed API documentation does not establish all applicable commercial access conditions.
Trello API introduction ↗
API key and authorization · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
The customer controls credentials or authorizes the application within existing resource permissions.
Trello API introduction ↗
Customer token authorization · Checked 2026-10-16
Downstream permission -
-
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
Applicable third-party processing, AI use and redistribution terms remain unresolved.
Trello API introduction ↗
Reviewed route documentation; downstream contractual scope unresolved · 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
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
Card create and update operations are documented.
Trello Cards REST API ↗
Create a new Card and Update a Card · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
Customers can connect an application using the documented token route.
Trello API introduction ↗
Customer application authentication · 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
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
Accessible board models can send change notifications.
Trello webhooks ↗
Creating a Webhook · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
Limits are 300 requests/10 seconds per API key and 100/10 seconds per token; member routes have additional limits and 429 responses.
Trello rate limits ↗
Limits and rate limit headers · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
updateCard and deleteCard identify supported card changes; coverage is scoped to these resources.
Trello action types ↗
Included Action Types · Checked 2026-10-16
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
Webhook retries are bounded; a durable replay checkpoint and complete recovery of excluded action types are unverified.
Trello webhooks ↗
Retries · 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
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
Structured files or API records can be held outside the provider.
Trello JSON export explanation ↗
Customer download route · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
The export guide does not establish a contractual post-cancellation retrieval window.
Trello JSON export explanation ↗
Reviewed export route; cancellation rights unresolved · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
JSON records are portable; complete independent restoration is unverified.
Trello JSON export explanation ↗
Reading JSON export · 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
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
External customer code can call the documented API; native logic portability is not established.
Trello API introduction ↗
Customer API integration · Checked 2026-10-16
Rights to custom logic -
-
Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes.
Ownership and reusable export of native workflow definitions require a separate contractual review.
Trello API introduction ↗
Reviewed route documentation; artifact rights unresolved · 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
A member authorizes an application token and chooses its permissions. Webhooks belong to that token and can monitor only accessible objects.
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
Board collections and card endpoints expose work records. Search and before/since action paging support targeted retrieval; action queries return at most 1,000 entries per request.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer API key and authorized member token | hybrid | Customer | No | Customer-supplied credentials | 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
Individual board JSON download and Premium CSV/workspace exports have different entitlements. The reviewed API pages do not establish the complete commercial condition for the customer API route.
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
REST documents creating, updating and deleting cards, plus attachments and checklists. Each action requires the relevant token permissions.
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
Board webhooks carry actions and changed models. Card deletion is a named action; excluded action types mean polling nested history cannot reconstruct every missed webhook.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. updateCard and deleteCard identify supported card changes; coverage is scoped to these resources. | Trello action types ↗Included Action TypesChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. Webhook retries are bounded; a durable replay checkpoint and complete recovery of excluded action types are unverified. | Trello webhooks ↗RetriesChecked 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
Board JSON and API records support planned extraction. Premium workspace exports offer a broader download route, but this assessment does not credit complete files, history or restorable automation.
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
Applications can implement external logic through card operations and webhooks. Rights to native automation definitions remain unresolved (a customer-held integration does not prove portable native rules).
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 scopeTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. Cards have structured fields and related-object endpoints. | Trello Cards REST API ↗Get a CardChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. Board collections and before/since action paging permit iterative retrieval. | Trello API introduction ↗Paging and ActionsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. Search queries select matching boards and cards. | Trello API introduction ↗SearchChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. The customer controls credentials or authorizes the application within existing resource permissions. | Trello API introduction ↗Customer token authorizationChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. Reviewed API documentation does not establish all applicable commercial access conditions. | Trello API introduction ↗API key and authorizationChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. Applicable third-party processing, AI use and redistribution terms remain unresolved. | Trello API introduction ↗Reviewed route documentation; downstream contractual scope unresolvedChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. Card create and update operations are documented. | Trello Cards REST API ↗Create a new Card and Update a CardChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. Customers can connect an application using the documented token route. | Trello API introduction ↗Customer application authenticationChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. Accessible board models can send change notifications. | Trello webhooks ↗Creating a WebhookChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. Limits are 300 requests/10 seconds per API key and 100/10 seconds per token; member routes have additional limits and 429 responses. | Trello rate limits ↗Limits and rate limit headersChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. Structured files or API records can be held outside the provider. | Trello JSON export explanation ↗Customer download routeChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. The export guide does not establish a contractual post-cancellation retrieval window. | Trello JSON export explanation ↗Reviewed export route; cancellation rights unresolvedChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. External customer code can call the documented API; native logic portability is not established. | Trello API introduction ↗Customer API integrationChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Trello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. Ownership and reusable export of native workflow definitions require a separate contractual review. | Trello API introduction ↗Reviewed route documentation; artifact rights unresolvedChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedTrello / customer-authorized API key and token, board/card REST resources, action history and board webhooks; Premium workspace exports and public Power-Up listing are separate routes. JSON records are portable; complete independent restoration is unverified. | Trello JSON export explanation ↗Reading JSON exportChecked 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
- Applicable downstream processing, AI-use and redistribution terms
- Contractual retrieval rights after cancellation
- Ownership and reusable export of native workflow artifacts
- Complete attachment, history and configuration migration
- Complete commercial entitlement for the assessed API route
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.