Call API header name error: "not legal"

[Northbridge_Recruitm]

Im not sure whether this is a bug or not, but im trying to set up a Call API action. The header is “Authorization: Bearer #API_Key#”

When i enter a custom value for the header as “Authorization: Bearer” followed by the API key as the value, i get this error:

Call API: TypeError: Authorization Bearer: is not a legal HTTP header name

I cant figure out any other way to set it up, but feel like i must be doing something wrong as “Authorization: Bearer” is commonly used for an authentication header…

[Jeff_Hager]

Check out this video and observe how the headers are set up for the authorization. I have a feeling you might be configuring it wrong.

Using Call API and Glide API to add rows to related tables. Also...JSON Object!

I wanted to show how you can use our new JSON columns to allow you use Call API into the Glide API. This allows you to create multiple rows in a different table and related them to the main table. Marco created a great video showing how this was done with an older method (before we had all the great new JSON columns) that used a combination of template fields but you can do this all with just a JSON Object column now. Here is a Loom video to explain. If I missed explaining anything feel free…

[Northbridge_Recruitm]

I am! you replied before i got a chance to delete my post - i made such an embarrassing error.

The header name should be “Authorization” and the value should be Bearer #API_Key#

Oops

[Jeff_Hager]

No worries. This might be good information for others that run into the same issue.