We’re making API requests even easier to prepare for programmers.

Firstly, please note that the current (or now, old) way of making API requests remains in place – no existing APIs are going to break!

The new style operates alongside the old and is described if you tick ‘use API’ in the ‘workflow – API’ panel for any view. The documentation 

https://docs.agilebase.co.uk/docs/integrations/setting-up-the-pull-api/

has also been updated.

Rather than the request needing four parameters, three of which are long IDs, no parameters are strictly necessary. You can just use a URL

https://cloud.agilebaseco.uk/agileBase/api.ab/mycompanyname/myviewid

The actual URL for each view, including mycompanyname and myviewid will be shown to you in the API panel for the view.

This is particularly useful for when you’re editing an API call on a phone or tablet, as you could be doing when creating a mobile app. It also makes it easier for AIs to use APIs – more on that coming in a future post. In general, it means there is less copying and pasting and fewer opportunities for errors when working with APIs.

Other updates

Many other improvements have made their way into this release, as follows.

• A usability improvement for tabs – using the ‘back to list’ button when editing a record inside a tab now ensures that changes you make are always reflected in the data shown in the list
• a bug causing an error to be displayed in rare circumstances, when a workflow button was pressed in a record, has been fixed
  
  Thanks to Chris Woodhams from new partners Lat51 Space Systems for reporting those two
  
• You can now change the default number of rows that is returned when a view is opened. The ‘default default’ if you like remains 25, but if you want to, you can now set it to any multiple of 25. In the properties panel for a view, scroll down to the bottom to see the new option
  
  Thanks to Luke Fullwood of the West of England Mayoral Combined Authority for requesting that
  
• Personal views are now clearly shown to be different to normal views when editing them, by the addition of the view owner’s icon at the top left of the editing panel.
  
  Thanks to Stephanie Lewis of The Vegan Food Group for alerting us to that need
  
• The ‘allow only given values’ option for tags fields is now properly utilised when importing from spreadsheet and in automated workflows, not just when users edit data on screen.
  
  We noticed that when onboarding new customer York House Foods
  
• In the developer interface, when looking at the list of tables, you can now see a breakdown of the total document storage used per table. That should help customers who wish to optimise storage costs.
  

Many more minor enhancements and tweaks have been made, if you are interested in seeing a full list please get in touch.

We hope these are useful and result in a generally better experience for all.