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
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Known file keys return structured document trees; comments use a separate endpoint.
Figma file endpoints ↗
GET file · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Repeat file requests for the declared key list; no whole-workspace enumeration is credited.
Figma file endpoints ↗
GET file and GET file nodes · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Node IDs, depth and version select file content.
Figma file endpoints ↗
GET file query parameters · Checked 2026-10-22
Access cost barrier 10.0/10
Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligible
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Starter resources receive an allowance; paid capacity depends on both seat and resource plan.
Figma rate limits ↗
Rate limit factors and Starter example · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 7.5/10
Open registration under published review criteria
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Public OAuth apps undergo Figma review; private apps have a narrower organizational audience.
Figma OAuth app publication and authorization ↗
Draft, private, and public OAuth apps · Checked 2026-10-22
Downstream permission -
-
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Applicable processing, AI-use and redistribution terms remain unresolved.
Figma OAuth app publication and authorization ↗
Access route; downstream rights unresolved · Checked 2026-10-22
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
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Comments can be posted or deleted by their author; design editing is outside this route.
Figma comment endpoints ↗
Post comments and Delete comments · Checked 2026-10-22
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Public apps can serve authorizing users after review.
Figma OAuth app publication and authorization ↗
Configure and publish a public OAuth app · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
FILE_UPDATE identifies edited files after the documented inactivity period.
Figma webhook event coverage ↗
FILE_UPDATE · Checked 2026-10-22
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Endpoint tiers, seats and resource plans determine limits; handle 429 using Retry-After.
Figma rate limits ↗
Rate limits and 429 responses · Checked 2026-10-22
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
FILE_DELETE identifies deleted files, excluding child files when their folder is deleted.
Figma webhook event coverage ↗
FILE_UPDATE and FILE_DELETE · Checked 2026-10-22
Replay and gap recovery 5.0/10
Bounded redelivery or overlapping queries; no durable consumer checkpoint
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Failed deliveries receive three retries; seven-day request diagnostics do not establish replay.
Figma webhook retries ↗
Configure your server and webhook requests · Checked 2026-10-22
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
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Scoped API records can be held outside the provider.
Figma file endpoints ↗
Documented structured read response · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
The reviewed access docs do not establish contractual retrieval rights after cancellation.
Figma OAuth app publication and authorization ↗
Access route; termination rights unresolved · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Portable records are documented; complete native restore and history remain unverified.
Figma file endpoints ↗
Read response and declared object scope · Checked 2026-10-22
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
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
External code can use the scoped API; native workflow portability is not established.
Figma OAuth app publication and authorization ↗
Application authentication · Checked 2026-10-22
Rights to custom logic -
-
Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded.
Native workflow ownership and reusable export rights require a separate contractual review.
Figma OAuth app publication and authorization ↗
Access route; native artifact rights unresolved · Checked 2026-10-22
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
Public OAuth apps need Figma review before customers can authorize them. Private apps serve their associated team or organization without that review.
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
Get file returns a selected file tree, with node and version selectors. Call comments and image endpoints separately; this is not automatic workspace discovery.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Reviewed public OAuth file application | oauth2 | partner | Yes | published review | 2026-10-22 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Starter resources have a small published API allowance. Paid seats and resource plans change the budget; do not apply a paid seat’s allowance to files in another plan.
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 assessed comment API posts and deletes comments. Only the author can delete a comment; this does not establish arbitrary design editing.
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
File update and deletion events carry file keys. Folder deletion does not notify every contained file; failed deliveries receive three retries.
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 resourcesFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. FILE_DELETE identifies deleted files, excluding child files when their folder is deleted. | Figma webhook event coverage ↗FILE_UPDATE and FILE_DELETEChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Bounded redelivery or overlapping queries; no durable consumer checkpointFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Failed deliveries receive three retries; seven-day request diagnostics do not establish replay. | Figma webhook retries ↗Configure your server and webhook requestsChecked 2026-10-22 |
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
File-tree JSON and comment records can leave Figma. Image URLs expire, and JSON alone is not a verified native design 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 write external integration code against the assessed API. Native workflow rights and independent execution remain unresolved (record access does not establish portable business logic).
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 scopeFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Known file keys return structured document trees; comments use a separate endpoint. | Figma file endpoints ↗GET fileChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Repeat file requests for the declared key list; no whole-workspace enumeration is credited. | Figma file endpoints ↗GET file and GET file nodesChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Node IDs, depth and version select file content. | Figma file endpoints ↗GET file query parametersChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Open registration under published review criteriaFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Public OAuth apps undergo Figma review; private apps have a narrower organizational audience. | Figma OAuth app publication and authorization ↗Draft, private, and public OAuth appsChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | Access is free, or included in the lowest paid plan with no fixed access fee; published usage-only charges are eligibleFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Starter resources receive an allowance; paid capacity depends on both seat and resource plan. | Figma rate limits ↗Rate limit factors and Starter exampleChecked 2026-10-22 |
| Which external write operations are documented? | Named operations in a limited domainFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Comments can be posted or deleted by their author; design editing is outside this route. | Figma comment endpoints ↗Post comments and Delete commentsChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Public apps can serve authorizing users after review. | Figma OAuth app publication and authorization ↗Configure and publish a public OAuth appChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. FILE_UPDATE identifies edited files after the documented inactivity period. | Figma webhook event coverage ↗FILE_UPDATEChecked 2026-10-22 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Endpoint tiers, seats and resource plans determine limits; handle 429 using Retry-After. | Figma rate limits ↗Rate limits and 429 responsesChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Scoped API records can be held outside the provider. | Figma file endpoints ↗Documented structured read responseChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Portable records are documented; complete native restore and history remain unverified. | Figma file endpoints ↗Read response and declared object scopeChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. The reviewed access docs do not establish contractual retrieval rights after cancellation. | Figma OAuth app publication and authorization ↗Access route; termination rights unresolvedChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedFigma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. External code can use the scoped API; native workflow portability is not established. | Figma OAuth app publication and authorization ↗Application authenticationChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Native workflow ownership and reusable export rights require a separate contractual review. | Figma OAuth app publication and authorization ↗Access route; native artifact rights unresolvedChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Figma / REST API reads for explicitly selected file keys and comments, comment posting/deletion and file webhooks through a public OAuth app. Design mutations, MCP, plugins and complete workspace migration are excluded. Applicable processing, AI-use and redistribution terms remain unresolved. | Figma OAuth app publication and authorization ↗Access route; downstream rights unresolvedChecked 2026-10-22 |
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
- Whole-workspace discovery and native design restore
- Recovery of child-file deletions after deleting a folder
- Applicable downstream terms where not established above
- Contractual post-cancellation retrieval rights
- Native workflow ownership, reusable definitions and complete product migration
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.