Is there a way to set create and set API
Is there a way to set create and set API Keys for the APIs?
18 Replies
Hi, you can pass the key as parameter in the Authorization Header of the REST API call to create key for your BuildShip API and access it in the next variables.
Also, if you are using Firebase, you can add authentication using Firebase Auth Trigger, docs - https://docs.buildship.com/trigger-nodes/firebase-auth
Firebase Authenticated User Trigger – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
A little confused by that.
pass the key as a paremeter and validate in the next node?
You can refer to this thread's first point - https://discord.com/channels/853498675484819476/1189598861602332774/1189619249438806036.
In case if you are looking how to store API keys and use across your project, you can refer - https://docs.buildship.com/secrets.
Discord
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
I'm sorry. This is still not working as expected. I'm trying to pass a key or string in the header. But my header auth and outside testing keep coming up as an error
Not understanding what I'm doing wrong here
Comes up blank even though I'm passing a header "Authorization : kkkkkkkkkk"
Can you share your workflow via in-app support? Or here is a simple workflow example of using auth header, you can paste this to a new workflow.
Same usecase here, they are using bool instead - https://discord.com/channels/853498675484819476/1194678089867862148.
I just need it to return the "Authorization" value so that I can then validate it to continue the workflow
I tried yours as well, Getting the same errors
Can you share your workflow via in-app support?
Yeah. I will
I created a micro version of the same issue
The return is getting the authorzation header, but coming back undefined.
I think I just found the problem. You can recreate and test auth headers in buildship