Glideapps Glide Big Tables API
Official vendor OpenAPI document · agent-readyStorageDatabasebearer13 EndpointsREST
For Agents
Read, write, and bulk-update rows in Glide Big Tables, manage staged stash uploads, and attach files to Glide app data.
Use for: I need to add new rows to a Glide Big Table from my pipeline, Update a single row in a Glide table by row ID, List all rows in a Glide Big Table, Create a new Big Table in Glide for my no-code app
Not supported: Does not render Glide app UI, run Glide actions, or edit columns/schema fields - use for Big Tables row data, file uploads, and job status only.
The Glide Big Tables API gives programmatic access to the data layer behind Glide's no-code app builder. Through it, applications and agents can create Big Tables, read and write rows in bulk or individually, monitor long-running data jobs, manage stash buffers for staged writes, and upload files that back image and document columns. It is the supported way to keep an external system of record (a warehouse, ETL job, or LLM pipeline) in sync with the data that Glide apps render to end users.
Install Jentic One Beta
Connect the Glide Big Tables API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Glide Big Tables API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fglideapps.com%2Fglideapps" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fglideapps.com%2Fglideapps" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Glide Big Tables API.
Provision a new Glide Big Table with a typed column schema for a no-code app
Append rows to a Big Table in batch from an upstream warehouse or scheduled job
Patch a single row in a Big Table by row ID without rewriting the rest of the table
Replace a Big Table's schema and data wholesale via PUT /tables/{tableId}
Initiate and complete multi-part file uploads that back image or document columns
Track asynchronous data jobs via GET /jobs/{jobId} until completion
Use Cases
Patterns agents use Glide Big Tables API for, with concrete tasks.
★ Warehouse-to-Glide ETL
Operations teams running a Glide front-end on top of a warehouse can keep tables in sync by writing scheduled jobs that POST new rows to /tables/{tableId}/rows and PATCH changed rows in place. The Big Tables API supports bulk writes and exposes a job ID per long-running operation, so the pipeline can wait for completion before notifying users. Setup is typically half a day for a single table.
POST 200 rows to /tables/{tableId}/rows, capture the returned job ID, and poll /jobs/{jobId} until status is complete.
AI-Generated Content Loaded Into a Glide App
An LLM pipeline producing summaries, tags, or images can write its output rows into a Big Table so a Glide-built internal tool surfaces the results to non-technical users. Files generated by the model (charts, PDFs) are uploaded via /uploads then referenced by URL in the row payload, keeping the no-code app fully data-driven.
Initiate POST /uploads, complete the upload via POST /uploads/{uploadId}/complete, then POST /tables/{tableId}/rows with a row referencing the uploaded file URL.
Agent-Maintained Operational Database
An AI agent given a Glide Big Table as its scratchpad can append research findings, update row status, and delete stale entries through the Big Tables API. Because each row CRUD operation is a single endpoint with a typed schema, the agent can write deterministically without parsing HTML or driving a UI.
Search Jentic for 'add row to glide big table', load the schema for POST /tables/{tableId}/rows, and write a new finding row with the agent's research output.
Key Endpoints
13 endpoints — the glide big tables api gives programmatic access to the data layer behind glide's no-code app builder.
METHOD
PATH
DESCRIPTION
POST
/tables
Create a new Big Table
GET
/tables/{tableId}/rows
Get rows from a Big Table
POST
/tables/{tableId}/rows
Add rows to a Big Table
PATCH
/tables/{tableId}/rows/{rowId}
Update a single row
DELETE
/tables/{tableId}/rows/{rowId}
Delete a row
POST
/uploads
Initiate a file upload
GET
/jobs/{jobId}
Check status of a long-running job
POST
/tables
Create a new Big Table
GET
/tables/{tableId}/rows
Get rows from a Big Table
POST
/tables/{tableId}/rows
Add rows to a Big Table
PATCH
/tables/{tableId}/rows/{rowId}
Update a single row
DELETE
/tables/{tableId}/rows/{rowId}
Delete a row
POST
/uploads
Initiate a file upload
GET
/jobs/{jobId}
Check status of a long-running job
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Glide Big Tables API by hand means learning its bearer auth and coordinating the row, upload, and async job endpoints yourself. Through Jentic you install once, import the Glide Big Tables API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Glide puts the table id in the URL path (/tables/{tableId}/rows/...), so a rule can pin your agent to one table: it can read and add rows there and nothing else. You choose the operations it may call, so destructive ones like deleting a row are not included unless you add them.
Credential isolation
Your Glide bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'add a row to a Glide table' or 'upload a file to Glide', and Jentic returns the matching Big Tables operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Glide Big Tables API through Jentic.
What authentication does the Glide Big Tables API use?
Glide uses HTTP bearer token authentication. Generate a token in the Glide dashboard and send it as Authorization: Bearer {token} on each request. Through Jentic the bearer token is held in the vault and never exposed to the agent.
Can I bulk-insert rows into a Glide Big Table?
Yes. POST /tables/{tableId}/rows accepts an array of rows in a single call and returns a job ID. Poll GET /jobs/{jobId} until the job reports complete to confirm the rows landed.
What are the rate limits for the Glide Big Tables API?
Glide does not publish a fixed rate limit in the OpenAPI spec; limits depend on your Glide plan. For high-volume jobs use the stash flow (PUT /stashes/{stashId}/data) so writes are buffered before commit instead of hammering /rows.
How do I update a single Glide row through Jentic?
Search Jentic for 'update glide row', load the schema for PATCH /tables/{tableId}/rows/{rowId}, and execute with the changed columns only. Run pip install jentic to start.
Can the Big Tables API attach files to row cells?
Yes. Initiate the upload with POST /uploads, complete it with POST /uploads/{uploadId}/complete, then write the resulting file URL into the relevant column when you POST or PATCH a row.
Is the Glide Big Tables API free?
API access is part of Glide's paid plans rather than the free tier. Check your Glide subscription before integrating; the API itself does not bill per call but is gated to plan eligibility.
Can I limit what my agent is allowed to do with the Glide Big Tables API?
Yes. Because you run Jentic One yourself, your own rules decide which Glide Big Tables operations and credentials the agent may use. Since the table id lives in the URL path, such as /tables/{tableId}/rows, you can pin the agent to a single table and grant only the calls you intend, for example reading rows with GET /tables/{tableId}/rows and adding rows with POST /tables/{tableId}/rows. Destructive operations like DELETE /tables/{tableId}/rows/{rowId} stay out of reach unless you explicitly include them.
GET STARTED