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
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
Glide API v2 operates only on Big Tables and remains in Public Beta. Other data-source types cannot use this route.
Glide API v2 Big Table row retrieval ↗
Get Rows pagination and row fields · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
Follow the Get Rows endpoint’s pagination token through the selected Big Table; retain the requested columns.
Glide API v2 Big Table row retrieval ↗
Get Rows pagination and row fields · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
Row selection and pagination use the Big Table endpoint. This review does not assume SQL support from the older queryTables API.
Glide API v2 Big Table row retrieval ↗
Get Rows pagination and row fields · Checked 2026-10-22
Access cost barrier -
-
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
Minimum plan eligibility for the assessed v2 Big Table route remains unconfirmed.
Glide API v2 scope and usage pricing ↗
Functionality, Public Beta and Pricing · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
The technical route is documented; eligibility and review for independently distributed third-party applications remain unresolved.
Glide API v2 authentication ↗
Bearer team token · Checked 2026-10-22
Downstream permission -
-
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
Glide API v2 authentication ↗
Bearer team token · Checked 2026-10-22
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
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
Add rows to a Big Table through the v2 row operation. API v1 mutation behavior is outside this assessment.
Glide API v2 add rows ↗
Add Rows to Table · Checked 2026-10-22
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
Glide API v2 authentication ↗
Bearer team token · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
Glide API v2 Big Table row retrieval ↗
Get Rows pagination and row fields · Checked 2026-10-22
Limit visibility 7.5/10
Numeric usage or polling guidance
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
Payloads are capped at 15MB/request; Add Rows supports approximately 250,000 rows/request, depending on size. A numeric request-rate budget remains unverified.
Glide API v2 limits ↗
Payload Limits and Row Limits · Checked 2026-10-22
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established.
Glide API v2 Big Table row retrieval ↗
Get Rows pagination and row fields · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified.
Glide API v2 Big Table row retrieval ↗
Get Rows pagination and row fields · 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
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
Glide API v2 Big Table row retrieval ↗
Get Rows pagination and row fields · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
Glide API v2 authentication ↗
Bearer team token · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
Glide API v2 Big Table row retrieval ↗
Get Rows pagination and row fields · 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
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
Glide API v2 authentication ↗
Bearer team token · Checked 2026-10-22
Rights to custom logic -
-
Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
Glide API v2 authentication ↗
Bearer team token · 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
The user’s bearer token is scoped to the team and can reach its applications and data. Keep it server-side and verify entitlement.
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
Follow the Get Rows endpoint’s pagination token through the selected Big Table; retain the requested columns. Row selection and pagination use the Big Table endpoint. This review does not assume SQL support from the older queryTables API.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Glide API v2 Big Table rows and row insertion | API key | Customer | Not confirmed | Not confirmed | 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
Minimum plan eligibility for the assessed v2 Big Table route remains unconfirmed.
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
Add rows to a Big Table through the v2 row operation. API v1 mutation behavior is outside this assessment.
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
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedGlide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established. | Glide API v2 Big Table row retrieval ↗Get Rows pagination and row fieldsChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedGlide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified. | Glide API v2 Big Table row retrieval ↗Get Rows pagination and row fieldsChecked 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
Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction.
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. Native workflow rights and independent execution remain unresolved (record access does not establish portable application 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 scopeGlide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. Glide API v2 operates only on Big Tables and remains in Public Beta. Other data-source types cannot use this route. | Glide API v2 Big Table row retrieval ↗Get Rows pagination and row fieldsChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsGlide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. Follow the Get Rows endpoint’s pagination token through the selected Big Table; retain the requested columns. | Glide API v2 Big Table row retrieval ↗Get Rows pagination and row fieldsChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersGlide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. Row selection and pagination use the Big Table endpoint. This review does not assume SQL support from the older queryTables API. | Glide API v2 Big Table row retrieval ↗Get Rows pagination and row fieldsChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | -Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. The technical route is documented; eligibility and review for independently distributed third-party applications remain unresolved. | Glide API v2 authentication ↗Bearer team tokenChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. Minimum plan eligibility for the assessed v2 Big Table route remains unconfirmed. | Glide API v2 scope and usage pricing ↗Functionality, Public Beta and PricingChecked 2026-10-22 |
| Which external write operations are documented? | Create and update in one business domainGlide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. Add rows to a Big Table through the v2 row operation. API v1 mutation behavior is outside this assessment. | Glide API v2 add rows ↗Add Rows to TableChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionGlide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. The documented interface can connect customer application code within its authorization and resource scope. | Glide API v2 authentication ↗Bearer team tokenChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsGlide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review. | Glide API v2 Big Table row retrieval ↗Get Rows pagination and row fieldsChecked 2026-10-22 |
| How are integration limits disclosed? | Numeric usage or polling guidanceGlide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. Payloads are capped at 15MB/request; Add Rows supports approximately 250,000 rows/request, depending on size. A numeric request-rate budget remains unverified. | Glide API v2 limits ↗Payload Limits and Row LimitsChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsGlide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | Glide API v2 Big Table row retrieval ↗Get Rows pagination and row fieldsChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | Glide API v2 authentication ↗Bearer team tokenChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedGlide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | Glide API v2 authentication ↗Bearer team tokenChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | Glide API v2 authentication ↗Bearer team tokenChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedGlide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. Retain the assessed structured records before losing access. Attachments, historical versions, permissions and full product configuration need separate extraction. | Glide API v2 Big Table row retrieval ↗Get Rows pagination and row fieldsChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Glide / Glide API v2 Big Table rows and row insertion; ordinary Glide Tables, computed-column parity, app layouts and full workspace migration are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | Glide API v2 authentication ↗Bearer team tokenChecked 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
- Downstream contractual permissions and post-cancellation retrieval rights
- Complete migration of history, files, permissions and native workflow definitions
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.