Glide Table API
Learn about the Glide Table API
If you're new to APIs, check out Glide Table API for Beginners ๐Ÿš€

Who has access to Glide API?

For Pro & Enterprise plans, every Glide Table has itโ€™s own API. With the API you can:
  • Add row to table
  • Set columns in row
  • Delete row

How do I access Glide API?

Open the Data editor Go to the Glide Table > right-click on the table icon on the left > show API usage This shows a window with the
To get started:
  1. 1.
    Open the Data editor
  2. 2.
    Go to the Glide Table > right-click on the table icon on the left > show API usage
  3. 3.
    This shows a window with the different text statements you can use.
When working with the API, you will pass a unique API Key, sometimes labeled a Bearer Token. It's a long sequence of random numbers and letters that looks like this: 2F2733E2-2B70-4291-8250-633B9E8F16AF You should treat this as a passwordโ€“it's a secret that you should not share.
Show API usage
If youโ€™re already experienced with APIs, you can view the reference doc below. If youโ€™re new to working with APIs or just need a step by step guide, we'll be posting more content very shortly.

mutateTables

This call enqueues one or more mutation operations for tables in an app in Glideโ€™s queue. When the call returns the actions will have been enqueued, but processing them can happen any time later. Actions that are enqueued are also not guaranteed to succeed.
For example, an action to delete a row that does not exist might successfully enqueue, but it will not be processed successfully. Note also that the actions are not guaranteed to be processed in sequence. For example, two added rows will not necessarily be added in the order they are given in the mutations array.
This call takes a JSON body of the following form:
1
{
2
"appID": "APP-ID",
3
"mutations": [MUTATION, ...]
4
}
Copied!
At least one mutation must be given. There is no definite or enforced upper bound on the number of mutations, but please keep it below 100.
The call will succeed if all mutations succeed, and fail if at least one mutation fails. It will return a JSON response thatโ€™s an array of results, one for each mutation. If a mutation fails then its result has a property error which is an error message.

Each mutation can be one of the following:

add-row-to-table

This mutation will add one row to a table in the app. It has this form:
1
{
2
"kind": "add-row-to-table",
3
"tableName": "TABLE-NAME",
4
"columnValues": {
5
"COLUMN-NAME": "COLUMN-VALUE",
6
...
7
}
8
}
Copied!
If the table has a row ID column, the result for the call, if successful, will have a property rowID with the row ID of the row to be added.
Not all columns have to be specified. Columns that are not specified will remain empty.set-columns-in-row

set-columns-in-row

This mutation will set one or more columns in an existing row:
1
{
2
"kind": "set-columns-in-row",
3
"tableName": "TABLE-NAME",
4
"columnValues": {
5
"COLUMN-NAME": "COLUMN-VALUE",
6
...
7
},
8
โ€‹
9
ROW-ID-OR-INDEX
10
}
Copied!
where ROW-ID-OR-INDEX is either
1
"rowID": "ROW-ID"
Copied!
or
1
"rowIndex": ROW-INDEX
Copied!
ROW-INDEX should only be used for Google Sheet tables. It must be a number, and itโ€™s zero-based, i.e. the first row in the sheet has index 0.

delete-row

This mutation will delete an existing row:
1
{
2
"kind": "delete-row",
3
"tableName": "TABLE-NAME",
4
ROW-ID-OR-INDEX
5
}
Copied!
ROW-ID-OR-INDEX is interpreted identically to set-columns-in-row.