# Weirdness writing to storage

**URL:** <https://forum.alumio.com/t/weirdness-writing-to-storage/1280>\
**Category:** Storages\
**Created:** [August 19, 2024, 6:56am UTC](https://forum.alumio.com/t/weirdness-writing-to-storage/1280 "2024-08-19T06:56:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jesse.wever](https://forum.alumio.com/user_avatar/forum.alumio.com/jesse.wever/32/296_2.png) [@jesse.wever](https://forum.alumio.com/u/jesse.wever)\
**Post date:** [August 19, 2024, 6:56am UTC](https://forum.alumio.com/t/weirdness-writing-to-storage/1280/1 "2024-08-19T06:56:05Z")

</div>

Hello everyone,

Currently i am in the process of connecting a new (to us) api to Alumio. this api uses some hybrid form of oauth and basic auth to connect so the standard http authentications weren’t a proper fit. I thought i could solve this by using the bearertoken from storage auth which works as advertised when manually saving the bearerToken which i got via Postman.

However getting the bearerToken into the storage from an entity transformer gives me some trouble. The response that i get looks like this:

```auto
{
    "access_token": "TestTokenInformationThatiShouldStore",
    "expires_in": 3600,
    "token_type": "Bearer"
}

```

When i have set the source of the “save entity to storage” set to &{access\_token} it write a null to the storage. How would i go and only store “TestTokenInformationThatiShouldStore” ?

scratch that i just figured it out XD. turns out i shouldn’t use the placeholders while the ui says i should

 ![afbeelding](https://alumio-forum.s3.dualstack.eu-central-1.amazonaws.com/uploads/original/2X/1/196abb4ef9a3a307de4d916f74f6b73e1941cb51.png)

---

<div class="post-metadata">

**Author:** ![jesse](https://forum.alumio.com/letter_avatar_proxy/v4/letter/j/c77e96/32.png) [@jesse](https://forum.alumio.com/u/jesse)\
**Post date:** [August 19, 2024, 7:38am UTC](https://forum.alumio.com/t/weirdness-writing-to-storage/1280/2 "2024-08-19T07:38:29Z")

</div>

@jesse.wever the ‘supports placeholders’ indication actually means that it can take the value of a placeholder as key to use as pointer for the source.

I.e. if the authentication request would contain an extra value such as ‘token\_field’ with value ‘access\_token’, you could use &{token\_field} which would trigger Alumio to find the ‘access\_token’ field and use that value as it’s source.

---

<div class="post-metadata">

**Author:** ![jesse.wever](https://forum.alumio.com/user_avatar/forum.alumio.com/jesse.wever/32/296_2.png) [@jesse.wever](https://forum.alumio.com/u/jesse.wever)\
**Post date:** [August 19, 2024, 7:57am UTC](https://forum.alumio.com/t/weirdness-writing-to-storage/1280/3 "2024-08-19T07:57:33Z")

</div>

ahh, then it makes sense it wouldn’t work. thanks for the information