# Matillion Extract APi Profiles and Api calls

**URL:** <https://matillioncommunity.discourse.group/t/matillion-extract-api-profiles-and-api-calls/1925>\
**Category:** Matillion ETL\
**Created:** [October 21, 2022, 9:12am UTC](https://matillioncommunity.discourse.group/t/matillion-extract-api-profiles-and-api-calls/1925 "2022-10-21T09:12:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![User1622461205189195283](https://avatars.discourse-cdn.com/v4/letter/u/82dd89/32.png) [@User1622461205189195283](https://matillioncommunity.discourse.group/u/User1622461205189195283)\
**Post date:** [October 21, 2022, 9:12am UTC](https://matillioncommunity.discourse.group/t/matillion-extract-api-profiles-and-api-calls/1925/1 "2022-10-21T09:12:27Z")

</div>

Hello

we created an API Extract Profile where we provided an bearer token and it could gather the schema

&nbsp;

when i'm now using this api extract component

and providing the same information

HEADER / QUERY Parameter and the bearer token it is complaining

&nbsp;

&nbsp;

with the following error message

The string needs to be in compact JSON format, which is of the form: '&lt;Base64UrlEncodedHeader&gt;.&lt;Base64UrlEncodedPayload&gt;.&lt;OPTIONAL, Base64UrlEncodedSignature&gt;'.

&nbsp;

hmm the bearer token was provided as the same in the api extract profile but now it is complaining

does anybody have some ideas ?

&nbsp;

thx Martin

&nbsp;

---

<div class="post-metadata">

**Author:** ![BenSmilesMatillionProductOwner](https://avatars.discourse-cdn.com/v4/letter/b/ba9def/32.png) [@BenSmilesMatillionProductOwner](https://matillioncommunity.discourse.group/u/BenSmilesMatillionProductOwner)\
**Post date:** [October 21, 2022, 1:17pm UTC](https://matillioncommunity.discourse.group/t/matillion-extract-api-profiles-and-api-calls/1925/2 "2022-10-21T13:17:34Z")

</div>

Hello Martin

&nbsp;

This is a known issue and has been fixed, with this fix being released in 1.67.6.

This should be available in the next week or so.

&nbsp;

Regards

Matillion Product Team

---

<div class="post-metadata">

**Author:** ![m.w](https://avatars.discourse-cdn.com/v4/letter/m/4af34b/32.png) [@m.w](https://matillioncommunity.discourse.group/u/m.w)\
**Post date:** [October 31, 2022, 1:47pm UTC](https://matillioncommunity.discourse.group/t/matillion-extract-api-profiles-and-api-calls/1925/3 "2022-10-31T13:47:42Z")

</div>

Hello Ben

we updated today to the newest Matillion 1.67.7 but we still get this API Extract component error - which you mentioned should be fixed (also according to the release notes)

but we still get the same error complaining about the compact json format

&nbsp;

do you have any idea why it is still not fixed?

thx Martin

---

<div class="post-metadata">

**Author:** ![BenSmilesMatillionProductOwner](https://avatars.discourse-cdn.com/v4/letter/b/ba9def/32.png) [@BenSmilesMatillionProductOwner](https://matillioncommunity.discourse.group/u/BenSmilesMatillionProductOwner)\
**Post date:** [November 1, 2022, 9:14am UTC](https://matillioncommunity.discourse.group/t/matillion-extract-api-profiles-and-api-calls/1925/4 "2022-11-01T09:14:27Z")

</div>

Hello Martin

&nbsp;

This definitely looks a little deeper than a Bearer Token Base64 encoding issue like I first suspected. This seems far more API specific.

Could I ask that you raise a support case for this so we could take a closer look. We'll need to see what API you are working with, how it's being setup (you don't need to provide a Bearer Token or any sensitive data) and the error message. We can then go from there.

&nbsp;

Thank you

Matillion Product Team

---

<div class="post-metadata">

**Author:** ![m.w](https://avatars.discourse-cdn.com/v4/letter/m/4af34b/32.png) [@m.w](https://matillioncommunity.discourse.group/u/m.w)\
**Post date:** [November 1, 2022, 10:55am UTC](https://matillioncommunity.discourse.group/t/matillion-extract-api-profiles-and-api-calls/1925/5 "2022-11-01T10:55:41Z")

</div>

Hi Ben I guess I checked again all settings and it seems now that with verison 1.67.7 it works

so I guess the Matillion bugfix resolved the issue

thx