Proper Format To Authenticate With API Key In The URL?

What is the proper way to authenticate with Bubble by adding the API Token directly in the URL for both the Workflow and the Data API as a querystring parameter api_token?

http://yourdomain.com/api/1.1/wf/endpoint_name

Can someone give me an example?

I really would recommend not doing that… however as per the docs…

You can also add your API Token directly in the URL for both the Workflow and the Data API as a querystring parameter api_token. This approach is not recommended as it is less secure.

so you just need to add something like ?api_token=xxxx to the end of the API url. xxxx would be your token.

1 Like

How are you supposed to authenticate then if the service you’re using to send a web hook does not allow you to send a key as a paramater??

You send in the headers. You should download https://www.getpostman.com/apps to play with this.
It will let you test the api call with setting headers.

I’ve tried it in postman but nothing is added to the url when you set up authorization in the Header.

The URL doesn’t get appended with the header information containing the api key. Am i doing something wrong?

No it doesnt add to the url - that is the point of using headers. When you send a request to any url… you are actually sending data in the header and the body. Information in the header tells the server what you want to do. You shouldnt care about seeing the header information so much… you should be checking the response is as you expect…

I would suggest that you see if you can get someone to help you with this… as it is very simple once you have seen it working :slight_smile:

This topic was automatically closed after 70 days. New replies are no longer allowed.