Is there a way to set create and set API
Is there a way to set create and set API Keys for the APIs?
GHi, 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.
GAlso, if you are using Firebase, you can add authentication using Firebase Auth Trigger, docs - https://docs.buildship.com/trigger-nodes/firebase-auth
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.
OA little confused by that.
Opass the key as a paremeter and validate in the next node?
GYou can refer to this thread's first point - Secure BuildShip endpoint access.
In case if you are looking how to store API keys and use across your project, you can refer - https://docs.buildship.com/secrets.
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 is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
OI'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
ONot understanding what I'm doing wrong here
OComes up blank even though I'm passing a header "Authorization : kkkkkkkkkk"
O
GCan 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.
message.txt5.88KB
GOI just need it to return the "Authorization" value so that I can then validate it to continue the workflow
OI tried yours as well, Getting the same errors
GCan you share your workflow via in-app support?
O
OYeah. I will
OI created a micro version of the same issue
OThe return is getting the authorzation header, but coming back undefined.
OI think I just found the problem. You can recreate and test auth headers in buildship
GCool, I looked at your workflow, and there is another workaround, we can also retreive the authorization header value directly without Get Authorization Node.
GAlso, as you have mentioned about learning more about the API specification in the support request, you can refer this - https://docs.buildship.com/basics/api-spec. It contains how to create authoirzation header and is use with example.
OThanks. I just got the authorization header to work in using Hoppscotch. I just couldn't test it directly in the app. (maybe a suggestion to have that in the test as you only have headers, query, body).