I’ve started using Airtable for almost everything that I used to pack into spreadsheets. The big advantage to using Airtable for your API is that they have an excellent visual user interface and integrations with many other tools built in. Plus, you can use Zapier to trigger custom actions when new items show up in Airtable.
Some of the advantages to using Airtable as a no-code API include:
Super simple to get started, a zero-code solution
Authentication via a single API key is very simple
Permissions using sharing settings in UI
Input forms to allow users to add content
Can use with Zapier to trigger events in other services, send emails, etc.
Database-style linking between records
Query by complex functions for advanced filtering and searching of records
User roles allow limited role-based permissions
Excellent automatic documentation generated for each table
API is automatic; every Airtable you make already has API access
Airtable is far from perfect. In fact, you’ll quickly run into its limitations if you have a lot of traffic and can’t cache the data. Some issues with Airtable as an API include:
Officially only allows up to 5 API requests per second, which might be fine for light use, but could be limiting as you scale up
Authenticating users requires them to have an Airtable account and generate their own API key
Single API key is not as secure as OAuth or similar server-client flow
Not as customizable as some options
Using Airtable is one of the simplest ways to turn your data into an API. You basically just have to create an account and set up a base.