# Call API header name error: "not legal"

**URL:** https://community.glideapps.com/t/call-api-header-name-error-not-legal/71356
**Category:** Ask for Help
**Created:** [March 2, 2024, 1:20pm UTC](https://community.glideapps.com/t/call-api-header-name-error-not-legal/71356 "2024-03-02T13:20:36Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)
#### Post date: [March 2, 2024, 1:40pm UTC](https://community.glideapps.com/t/call-api-header-name-error-not-legal/71356/2 "2024-03-02T13:40:52Z")

</div>

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!](https://community.glideapps.com/t/using-call-api-and-glide-api-to-add-rows-to-related-tables-also-json-object/70860):
>
> 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](https://www.youtube.com/watch?v=b7_k3_brusQ&t=6s) 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](https://www.loom.com/share/041b3cf99dec42c1a4d25af8c7aee38f) to explain. If I missed explaining anything feel free…

---

_[View the full topic](https://community.glideapps.com/t/call-api-header-name-error-not-legal/71356)._