Hi - looking for some quick clarification on the levels of access to Glide API.
I was building an action in order to delete all child tasks associated with a parent project, when that parent project is deleted. The quickest and easiest way I saw to do this was just to create a cURL API call, and have the action use the joined list in my table to call Delete Row. So I’m not attempting to pull in external data using the API, or push data out from my tables to another service. This is all internal to my own tables.
In order to “Show API” for tables, I upgraded to Team account. However, when I went to actually call the Glide API in the action editor, I’m not able to access - says I need to upgrade again to Business account.
Am I missing how to execute this action somewhere? Or possibly attempting to use the wrong API? All of the documentation says that Team accounts come with Basic API that allows you to “Use the GLIDE BASIC API to add, update, and delete data within Glide tables directly”. I’m not currently seeing how to call the basic API without upgrading again.
The Get Row mutation requires a Business plan, but deleting rows is really easy. You can simply delete rows through a multiple relation without having to bother with an API.
I didn’t realize you could delete rows with multiple relations. That works perfectly for this specific use case. Thanks for that.
Any idea why Glide allows for multiple relation DELETE, but not multiple relation ADD?
I’m still somewhat confused on the specifics of the API access at the Team level based on what you said. Has something recently changed that has documentation (and all marketing) outdated? What’s the difference in what you’re calling a Get Row Mutation vs what glide means when saying you can use Basic API to add/update/delete within tables directly?
In other posts/videos, people have referenced “Integrations → Generic API → Call API” being available in the action editor. The only API access I’m seeing is under “Communications → Call API”, and that’s listed as needing Business/Enterprise account.
If you don’t have access to Call API, then the next best option is a Trigger Webhook to Make, and then use a Make HTTP module (or the new Glide module) to call the Glide API.
That’s exactly what I was looking at as a backup option. Good to know. Thanks.
I’m thinking at some point the actual access to those two different endpoints were split. Now there appears to be only one. I know there have been previous legacy accounts, then Pro levels, now Teams. There are multiple articles and videos (from about 6 months ago, back to 12-15 months ago) that show add/update/delete being under Generic API or Basic API, and then a separate API Call for the Get Rows / Query.
Sorry, I think I misread your original post. I think I was under the impression that you were trying to use the API to first get all rows, and then read through them to formulate your delete mutations. Hopefully I didn’t confuse you too much.