Easiest way to get API output on web pages?
I'm mulling over a project that would involve piping API output onto a series of web pages...
- An "index"/home page, which would show output from one or more API requests.
- A series of site.com/company/{name} pages, wherein the site should throw the dynamic {name} from the URL string at an API endpoint and display the result.
API in question would probably be Airtable.
I would want to do some basic front-end design for this.
I can conceive of doing this with PHP and Bootstrap. That said, I probably don't yet have all the PHP skills for this.
Anyone know of a nice way to do this using no/low code?
Not very interested in syncing stuff to Webflow CMS and using that.
Thanks.
Trending on Indie Hackers
You can't use the Airtable API directly from a web page. So, you'll have to learn how to call the API from PHP.
Why aren't you interested in using something to sync Airtable to Webflow CMS? Is it because you've had bad experiences doing it with Zapier or Integromat?
There are easier solutions. I built PowerImporter to sync Airtable to the CMS. It's the easiest way to get your Airtable data into Webflow, and keep them in sync.
No.
I don't actually use Webflow at this point.
Any of my skills background is around PHP for WordPress.
Everyone talks about Webflow within the nocode web bracket but, to me, it looks like a full-fledged web design tool a la Frontpage, which necessarily has a learning curve.
I am interested in the idea of moving off WordPress etc, toward simpler, nocode tools. I'm just struggling with the idea of investing the time in developing my skills in an area like Webflow, which theoretically could make future development easier thanks to nocode, when it necessarily needs getting to grips with, too.
That's why I'm feeling out options including:
Webflow has Webflow CMS. But I think my data/content exists elsewhere and is accessible via API response.
In my mind, Webflow should just be able to help me show that content. Not sure I want to go through syncing it, which is one step removed from the actual source content. And then also gets me into working within Webflow CMS' records limits etc.
Still, a lot of this is at the theoretical level for me at the moment, so it may well be that I end up there.
In fact, it may be that I don't take content from Airtable at all. At present, my content is accessible via the RSS reader Inoreader, which has its own API, for which there is a PHP library. Inoreader is the content's primary source. Copying it to Airtable would already represent duplication, and copying it to Webflow would be yet another step. I think I would only end up copying that to Airtable if I discover some need to, which is possible but not initially.
Thanks for the reply.