Hi! I’m trying to make an HTTP request between Make and Missive, missive requires authentication via bearer tokens that should be included on the http request header. I believe I have done this (Screenshots attached below) but still getting a 401 error. Would love to get help from the community. Thank you!
You should be using the HTTP module “Make an API Key Auth request”.
You should try this brand new course/tutorial in the Make Academy on how to use external APIs — API calls with HTTP modules
- API and Endpoints
- Header and body
- Multipart/form-data
- OAuth 2.0
samliew – request private consultation
Join the Make unofficial Discord server!
Hello! Thank you for the reply! and the link to the course! also - I tried to follow what you did and I still got a 401 Error. I’m 100% sure that I have the correct token too.
Make sure in the Key field, you have to type Bearer
with a space after Bearer, followed by the key and no additional spaces.
Otherwise, you might have requested a new token, and you simply need to set up a new connection with the new key, because the old one is no longer valid.
samliew – request private consultation
Join the Make unofficial Discord server!
Yeah I made sure to have the "Bearer " in there as well before the Token.
Did you try setting up a new connection with the new key?
Or did your Missive admin disable external API access?
Yesss. I even tried generating a new Missive Key and creating a new connection with the new Missive Key. I’m also the admin of our Missive Org. and API access is enabled.
Well, I’ve tried my best but I can’t help you any further unless I have access to your Missive team.
Thanks so much for your time!
Bearer tokens are generated as a result of an oAuth usually and can expire. Do you have the ability to generate them? or are you actually creating a client ID and client secret instead to be used as part of an oAuth authentication. The Missive API docs will tell you the proper authentication flow required, but in my experience you cannot generate Bearer tokens in a UI but rather they are generated for you as a result of an oAuth authorization process.