No code/low code way to integrate with third party API that uses basic authentication?

[Tushar_Sheth]

I am using Airtable as the backend for my hiring assessment app (a cybersecurity hiring test). As I understand it, Airtable’s API uses bearer authentication.

I’m trying to integrate my app with Greenhouse.io, an applicant tracking system. Greenhouse’s API uses basic authentication.

The way it works is this:

1. Our customer, which uses Greenhouse to manage its hiring process, gets a list of tests (assessments) from us with a GET call.
2. Customer chooses which test they’d like a particular candidate to take, and gives us the details with a POST call.
3. We send the test to the candidate.
4. We let the customer know when the assessment is complete with a PATCH call.
5. Customer gets the assessment results from us using a GET call.

Is there a no code/low code way for me to integrate with the Greenhouse API even though they use a different authentication method?

[Tushar_Sheth]

Thanks. Would Integromat, Zapier, or some other option allow me to somehow receive a GET request and then send data from somewhere back to Greenhouse in response?

[ScottWorld]

Absolutely! In Integromat, you would just use their HTTP module to create any sort of API requests that you’d like. See link below.

But you definitely don’t want to use Zapier, because they don’t offer full Airtable support (and Integromat is a more advanced platform, in general).

If you need my help setting all of this up for you, just let me know!

Integromat Support

HTTP

The HTTP app provides various modules for communication based on Hypertext Transfer Protocol (HTTP). HTTP is the foundation of data communication for the World Wide Web. The modules enable you to d...

[Smoked_Haddock]

https://autocode.com/ might interest you, it’s like Zapier but with full-on scripting, and Airtable access built-in. I use it to extract and reason about the text content of newly uploaded pdf attachments and rate it highly.

[Bill_French]

Smoked_Haddock:

https://autocode.com/

This is a smart recommendation. I’ve experimented with autocoder and it fits into an API strategy that works well for many requirements. And the free tier is quite generous.

[Olpy_Acaflo]

Smoked_Haddock:

https://autocode.com/

Interesting ! Thank you @Smoked_Haddock and @Bill.French.

This is autocode DOCUMENTATION.

olπ

[Olpy_Acaflo]

Am I mistaken or does autocode seem to be a kind of ‘user friendly’ layer of abstraction on top of what AWS called Lambda when I learned about it in the fall of 2018 before running away due to lack of time to get into it?

[Olpy_Acaflo]

Am I mistaken or does autocode seem to be a kind of ‘user friendly’ layer of abstraction on top of what é DoubleU S called Lambda when I learned about it in the fall of 2018 before running away due to lack of time to get into it?

[Bill_French]

Olpy,

I saw your question about AWS/Lambda and you are partially right, but it’s more nuanced.

The impetus for creating FunctionScript is simple: it stems from the initial vision of Standard Library. We believe the modern web is missing a base primitive - the API. Daily, computer systems and developers around the planet make trillions of requests to perform specific tasks: process credit card payments with Stripe, send team messages via Slack, create SMS messages with Twilio. These requests are made primarily over HTTP: Hypertext Transfer Protocol. However, little to no “hypertext” is actually sent or received, these use cases have emerged in an ad hoc fashion as a testament to the power of the world wide web. Oftentimes, API standardization attempts have been presented as band-aids instead of solutions: requiring developers to jury rig a language, framework, markup language and hosting provider together just to get a simple “hello world” out the door.

By creating API development standards as part of a language specification instead of a framework, FunctionScript truly treats the web API as a base primitive of software development instead of an afterthought. This allows teams to be able to deliver high-quality APIs with the same fidelity as organizations like Stripe in a fraction of the time without requiring any additional tooling.

FunctionScript has been developed by the team at Polybit Inc., responsible for Standard Library. Ongoing development is, in part, funded by both Stripe and Slack as venture investments in the parent organization.

If you dig deep into the heritage of Standard Library you can see how (and why) autocode emerged as it did. It’s a long but somewhat interesting story of why the interweb has become one of the cornerstones of the API economy.

FunctionScript truly treats the web API as a base primitive of software development instead of an afterthought.

This is the key issue - the argument (for FunctionScript and autocode) is that HTTP(s) is an inadequate and antiquated protocol for building application interchange processes. No one can debate this. However, we can all debate how to modernize the web to accommodate and hypercharge the API economy. :winking_face:

[Olpy_Acaflo]

Thank you very much @Bill.French for this new pedagogical contribution rich in content and arguments.
And thank you for your teaching in this Community in general: be sure that you are influencing me: after avoiding what you call “glu factories” and “nice friendly cul-de-sac” too, I continue to keep in mind to avoid problematic practices when I try to integrate, to automate.
Of course, for a small individual account, the credit card is often the first limit, but as I am not afraid to script by myself, I have been able to evolve by reading you and the generous Experts of their time and knowledge here.
olπ

[Bill_French]

Olpy_Acaflo:

I have been able to evolve by reading you and the generous Experts of their time and knowledge here.

You are so kind. Appreciate the comments.

Olpy_Acaflo:

pedagogical contribution rich in content and arguments.

I love your prose. :winking_face: Even Dennis Miller would have a difficult time keeping up with you.