I'm posting a message and THEN scrolling

[hollow minnow]

Get this even when using a proper Bearer token that's a resend api key re_***

[grave oar]

we will get someone from the team to help you, stay tuned!

[hollow minnow]

Just in the FWIW category, the simple API I'm also testing against is the Monica CRM API, pretty basic stuff
(https://www.monicahq.com/api/overview)

[hollow minnow]

Any luck?

It's as if all external calls are disallowed. No tool works with authenticated API calls

[junior stream]

How is your setup in tools? Can you make sure api_key actually works over curl request or postman something

if it's the case probably tools setup is having problem or we have a problem, which can be nice to get more info to debug

[hollow minnow]

I have checked and can make api requests and get responses from a variety of different methods, but not when using an agent id and elevenlabs conversations.

Tools setup has a problem

It's almost like a CORS issue, or a missing headers in the server side process of the tool code

[hollow minnow]

yeah, pretty basic

[junior stream]

could you send me the agent-id and conversation-id from private message where it's failing I will try to recreate issue on my side

[hollow minnow]

Any updates?

[junior stream]

@hollow minnow it's your resend error, In the example it's called bearer because that's the name of the api token in cal.com.

Call it whatever it called in resend, tool calling itself is working, other clients use with different usecases as well. I can't see how resend authenticate over api at all

[hollow minnow]

Nah, that's not correct. You need to be able to clearly describe what variable is being used in what spot and how it looks. Just sending me a screenshot of cal.com isn't super helpful. I've seen this. And tried my best to follow along.

That "string" includes the word "Bearer "

but that's NOT what the Secret wants.

are you a dev at 11?

I'm just trying to ascertain how you are taking these form variables and applying them to the header before sending the request on the server

And just so we are clear.
https://resend.com/docs/api-reference/introduction

It's right in the docs. Anyone can access and see them.

It's public.

[spice sandal]

Im having a similar issue with SendGrid

[spice sandal]

I think the tools just are not working period.

[hollow minnow]

agreed

[hollow minnow]

Rough ya'll.

[floral palm]

Hey @hollow minnow apologies for the delay replying to this.

The issue is that your tool is set up with a malformed header.

This is the correct API structure for Resend:

curl -X GET 'https://api.resend.com/api-keys' \
     -H 'Authorization: Bearer re_REDACTED' \
     -H 'Content-Type: application/json'

Your Webhook would send a response that looks like this:

curl -X GET 'https://api.resend.com/api-keys' \
     -H 'Bearer: re_REDACTED' \
     -H 'Content-Type: application/json'

You need to:

• Update your Resend_Bearer secret from: re_REDACTED to Bearer re_REDACTED
• Update the authentication header name from Bearer -> Authorization

I realise this is pretty confusing - will propose that we add a cleaner method for adding dedicated authentication headers to tools.

[hollow minnow]

Long since addressed.

Thanks for the update however.

Good to know there's at least a team behind the company 🙂

[floral palm]

Feel free to e-mail me with anything else [e-mail]

Great feedback though so thank you