Notifications
Clear all
How To
14
Posts
5
Users
0
Reactions
5
Views
Topic starter
I'm encountering a 401 error: {"error_message":"Authorization header with scheme ‘Bearer’ required"}. This is happening even though I've correctly entered the bearer API key. The API key is directly from callin.io and is accurate, and there's no mention of "Bearer key_feb5c898dr8e8b2f50ba54071118" (which is a fake API key).
This is quite frustrating as I've used the exact same configuration successfully in other workflows without any problems. I've attempted to recreate the setup multiple times, and each instance yields the same error. Does anyone have any suggestions?
Posted : 13/01/2025 1:42 am
Hey
You have to pass the authorization in the following way:
BearerYour API key
Regards,
Msquare Automation - Platinum Partner of callin.io
Posted : 13/01/2025 9:39 am
Topic starter
I've removed the extra space, and I'm still encountering the same error message.
Posted : 13/01/2025 2:49 pm
Hi,
Could you please share a screenshot of the module's configuration? Other community members might be able to identify a problem.
Regards, Terry.
Posted : 13/01/2025 3:53 pm
Hello everyone,
Experiencing the exact same problem here. Does anyone have any suggestions?
My API token functions correctly when used with Postman or via curl.
Posted : 13/01/2025 7:18 pm
Topic starter
Are you suggesting I should use Postman via cURL to achieve this? If so, could you explain how? I'm aiming to use GoHighLevel to initiate the campaign, but the HTTP request isn't recognizing my API.
Posted : 13/01/2025 7:51 pm
Hi,
I see you're using a "Basic Auth" key and have also included a Bearer token. These represent two distinct authentication approaches.
- You have the option to utilize the "Make an API Key Auth request" HTTP module, allowing callin.io to manage your API key storage (in this scenario, you won't need to add any headers).
OR - Alternatively, you can employ the "Make a request" HTTP module and manually add your Authorization headers. In this case, callin.io will not prompt you to establish a connection.
Personally, I tend to favor the "Make a request" HTTP module as it offers me the greatest flexibility in dictating what is transmitted to my APIs.
Regards, Terry.
Posted : 13/01/2025 8:22 pm
Hi
I’m saying my API token works in other platforms.
Posted : 13/01/2025 9:07 pm
Topic starter
Okay, I'll give this a shot and report back.
Posted : 13/01/2025 9:11 pm
Topic starter
Hey Terry, that worked! Thanks! Now I'm encountering an issue where the "to_number" isn't recognizing my number. I'm receiving a "400" error code due to the number format not being E.164.
I appreciate your assistance with this matter.
Thanks again!
Posted : 14/01/2025 10:39 am
Hi,
That’s great. I’m happy it was successful.
Could you please mark my response as the solution? This will help other users find the answer quickly if they encounter the same issue. It looks like you’ve currently marked your own reply as the solution.
Best regards, Terry.
Posted : 16/01/2025 2:13 am
Hi,
Have you considered using the “Make a request” HTTP module, similar to the approach shown in this response:
Best regards, Terry.
Posted : 16/01/2025 2:14 am