It would be JUICY if we could get a loose timeline on this, and if the current normal glide tables will be migrated on the back end automatically when this happens. 
1 Like
Hey! is there any update usage for the get row version api that returns an etag?
EDIT: I’ve found it in the docs! 0’s the answer , nice!
2 Likes
Bump to ask if anyone is planning to make a MAKE.COM module to use this V2 API Processing model?
1 Like
The pricing for the Make integration is separate from the pricing of the Glide API, so there are no plans at this moment.
2 Likes
In theory could someone not create a custom make.com module though and access the v2 api in that fashion?? Seperate from the current glide~make integration currently offered.
1 Like
Yeah, you can build custom modules as long as you are familiar with the API and the Make syntax.
Their modules are essentially wrappers around API endpoints.
1 Like
I’ll pay someone to build it. It will help the community save on updates! DM me if you have the capability! I would learn it and do it but I’m swamped with projects
1 Like
Can we please get API filtering capabilities? It’s a significant roadblock for us at the moment.
1 Like
Do you mean something like SQL query inside API calls?
1 Like
Thinking along the lines of query params inside the api call URL.
So instead of getting a whole table back of results by calling the following:
The ability to add query parameters like:
GET https://api.glideapps.com/tables/{projTableID}/rows/?projLead=jdoe&status=inProgress
1 Like
You can use this on v1 for Big Tables.
Not the same URL params as you said, but it’s the same concept.
1 Like
I saw that, thank you. Hopefully v2 will have something comparable soon.
2 Likes
Can we use query parameters like V1 for glide tables? This would speed up my executions drastically, currently I have to call all the rows, then filter them in the next step for just the jobId I want…
1 Like
That’s not available for Glide Tables as of now. Only Big Tables have params like the doc I linked above.
1 Like