# API refresh token

**URL:** <https://community.squaredup.com/t/api-refresh-token/1315>\
**Category:** Dashboard Server\
**Created:** [March 8, 2021, 4:22pm UTC](https://community.squaredup.com/t/api-refresh-token/1315 "2021-03-08T16:22:25Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cragdoo](https://community.squaredup.com/user_avatar/community.squaredup.com/cragdoo/32/872_2.png) [@Cragdoo](https://community.squaredup.com/u/Cragdoo)\
**Post date:** [March 8, 2021, 4:22pm UTC](https://community.squaredup.com/t/api-refresh-token/1315/1 "2021-03-08T16:22:25Z")

</div>

Hello

Looking into the new Dashboard Server, and Web API integration in particular. In the past the Web API tile allowed you to specify the refresh token url, but doesn’t appear to be the case in this version. Just wondering how the Web API handles expiring access tokens?

---

<div class="post-metadata">

**Author:** ![Cragdoo](https://community.squaredup.com/user_avatar/community.squaredup.com/cragdoo/32/872_2.png) [@Cragdoo](https://community.squaredup.com/u/Cragdoo)\
**Post date:** [March 8, 2021, 5:08pm UTC](https://community.squaredup.com/t/api-refresh-token/1315/2 "2021-03-08T17:08:34Z")

</div>

nm …got it …had setup the wrong authentication type in the integration.

---

<div class="post-metadata">

**Author:** ![john-knowles](https://community.squaredup.com/user_avatar/community.squaredup.com/john-knowles/32/934_2.png) [@john-knowles](https://community.squaredup.com/u/john-knowles)\
**Post date:** [March 9, 2021, 2:31pm UTC](https://community.squaredup.com/t/api-refresh-token/1315/3 "2021-03-09T14:31:28Z")

</div>

Glad you found the answer! We can’t wait to hear what you think 🙂

---

<div class="post-metadata">

**Author:** ![Cragdoo](https://community.squaredup.com/user_avatar/community.squaredup.com/cragdoo/32/872_2.png) [@Cragdoo](https://community.squaredup.com/u/Cragdoo)\
**Post date:** [March 9, 2021, 4:10pm UTC](https://community.squaredup.com/t/api-refresh-token/1315/4 "2021-03-09T16:10:55Z")

</div>

one step forward , 2 steps back

the API supplier (in this case Veeam) has a requirement for a header

```
"x-api-version: 1.0-rev1"

```

What’s the best way to incorporate this when setting up an OAuth Web API integration?

---

<div class="post-metadata">

**Author:** ![Adam](https://community.squaredup.com/user_avatar/community.squaredup.com/adam/32/763_2.png) [@Adam](https://community.squaredup.com/u/Adam)\
**Post date:** [March 9, 2021, 4:16pm UTC](https://community.squaredup.com/t/api-refresh-token/1315/5 "2021-03-09T16:16:10Z")

</div>

Hey Craig, there isn’t currently a means to add a header to an Oauth provider at the provider level. You’d need to set that extra header within your tile.  
 ![image](https://community-cdn.squaredup.com/original/1X/d2b3dde33357b88c9637ba3aa61f9e7affc6194d.png)

This would be necessary for every tile using that provider. I’m sure @john-knowles will get this added to the feature requests queue for you. Very valid requirement 🙂

---

<div class="post-metadata">

**Author:** ![Cragdoo](https://community.squaredup.com/user_avatar/community.squaredup.com/cragdoo/32/872_2.png) [@Cragdoo](https://community.squaredup.com/u/Cragdoo)\
**Post date:** [March 9, 2021, 4:40pm UTC](https://community.squaredup.com/t/api-refresh-token/1315/6 "2021-03-09T16:40:07Z")

</div>

Thanks Adam, might need to try a different API provider then for my testing ☹

---

<div class="post-metadata">

**Author:** ![john-knowles](https://community.squaredup.com/user_avatar/community.squaredup.com/john-knowles/32/934_2.png) [@john-knowles](https://community.squaredup.com/u/john-knowles)\
**Post date:** [March 9, 2021, 6:24pm UTC](https://community.squaredup.com/t/api-refresh-token/1315/7 "2021-03-09T18:24:34Z")

</div>

Unless I am miss understanding the problem, you can still use this provider @Cragdoo, just remember to put the header into the tile when you configure it on the dashboard. Just like @Adam’s screenshot.

> **[How to use the Web API tile](https://support.squaredup.com/hc/en-us/articles/360017706317-How-to-use-the-Web-API-tile#headers--data)**
>
> The Web API tile allows you to pull data from external web sources and display this data using a variety of visualisations. For example, retrieving a list of events from Splunk, or displaying figur...

I’ll log the suggestion too, thank you!

---

<div class="post-metadata">

**Author:** ![Adam](https://community.squaredup.com/user_avatar/community.squaredup.com/adam/32/763_2.png) [@Adam](https://community.squaredup.com/u/Adam)\
**Post date:** [March 9, 2021, 6:39pm UTC](https://community.squaredup.com/t/api-refresh-token/1315/8 "2021-03-09T18:39:49Z")

</div>

It’ll work @Cragdoo, I just meant that you can’t specify it once within the provider config. Add your provider and try configuring a tile, just remembering to set that API version header in the Headers & Data panel. That way it’ll get sent with the request when the dashboard loads and your API should respond just fine.

---

<div class="post-metadata">

**Author:** ![Cragdoo](https://community.squaredup.com/user_avatar/community.squaredup.com/cragdoo/32/872_2.png) [@Cragdoo](https://community.squaredup.com/u/Cragdoo)\
**Post date:** [March 10, 2021, 9:33am UTC](https://community.squaredup.com/t/api-refresh-token/1315/9 "2021-03-10T09:33:09Z")

</div>

> [@Cragdoo](#):
>
> `"x-api-version: 1.0-rev1"`

Thanks Adam/John

The issue is when I try to add the OAUTH integration, the API provider needs the header, even on the initial authorisation. I’m speaking to Veeam about this.

In the meantime, Adam I will take you up your offer for a 30 mins chat, next week sometime. Would be good to discuss.

---

<div class="post-metadata">

**Author:** ![Cragdoo](https://community.squaredup.com/user_avatar/community.squaredup.com/cragdoo/32/872_2.png) [@Cragdoo](https://community.squaredup.com/u/Cragdoo)\
**Post date:** [May 13, 2021, 12:20pm UTC](https://community.squaredup.com/t/api-refresh-token/1315/10 "2021-05-13T12:20:52Z")

</div>

back to the original topic about refresh tokens. I’ll still seeing, what appears to be, my session token expiring, but not renewing/refreshing. I’m trying to figure out if it’s a me/Veeam/Squared up issue. Any guidance?/info about how the Web API integration handles refresh tokens?
