# API and Sandbox periods

**URL:** <https://community.silverfin.com/t/api-and-sandbox-periods/239>\
**Category:** API\
**Created:** [May 8, 2017, 5:45am UTC](https://community.silverfin.com/t/api-and-sandbox-periods/239 "2017-05-08T05:45:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![JorisJoppe](https://avatars.discourse-cdn.com/v4/letter/j/8491ac/32.png) [@JorisJoppe](https://community.silverfin.com/u/JorisJoppe)\
**Post date:** [May 8, 2017, 5:45am UTC](https://community.silverfin.com/t/api-and-sandbox-periods/239/1 "2017-05-08T05:45:25Z")

</div>

We use Sandbox to develop an integration w/ Silverfin. A few questions:

- Our sandbox only refreshes to upto period 2015-09. Are we doing something wrong or is this a hard setting?

- We use the get-request for financials which requires a period-id. This is a numerical value that can be obtained from the periods-call. Is there a logic we can use to determine the period-id related to a calendar period (to avoid the periods-call). Such as: period\_id 49 == 2015/01

Or alternatively - is it possible to create the financials call with a period-parameter rather than a period\_id parameter (the first option is the more common option in our experience).

---

<div class="post-metadata">

**Author:** ![Tim](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.silverfin.com/tim/32/1304_2.png) [@Tim](https://community.silverfin.com/u/Tim)\
**Post date:** [May 8, 2017, 7:57am UTC](https://community.silverfin.com/t/api-and-sandbox-periods/239/2 "2017-05-08T07:57:42Z")

</div>

Hi @JorisJoppe,

- Are you sure there’s more data available in your test environment? This is not a hard setting and should synchronize as much data as there is available
- We’re working with a `period_id` right now because periods can also be archived/deleted and be replaced by a new period for the exact same end date. You can’t extrapolate anything from the `id`.

I’ll have a look if there’s something we could add here, but this will probably not be for the near future. I would advise to just fetch all periods currently and make some internal hash to find the id you’re looking for.

btw, in the last week we’ve added a parameter `bot_name` to the remarks api, so you can make it explicit that the remark was posted by a bot iso the owner of the access token.

---

<div class="post-metadata">

**Author:** ![JorisJoppe](https://avatars.discourse-cdn.com/v4/letter/j/8491ac/32.png) [@JorisJoppe](https://community.silverfin.com/u/JorisJoppe)\
**Post date:** [May 8, 2017, 12:25pm UTC](https://community.silverfin.com/t/api-and-sandbox-periods/239/3 "2017-05-08T12:25:14Z")

</div>

thanks @Tim

Data in EOL (division code 171930) runs upto jan-2017 (at least one entry in that period).

As for `period_id`: this is a bit of problem in the way our process is built but lets see on our end if we can build something for this (might not be in place before Tuesday but it will still work).

We will see if we can implement `bot_name`

---

<div class="post-metadata">

**Author:** ![Tim](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.silverfin.com/tim/32/1304_2.png) [@Tim](https://community.silverfin.com/u/Tim)\
**Post date:** [May 8, 2017, 3:55pm UTC](https://community.silverfin.com/t/api-and-sandbox-periods/239/4 "2017-05-08T15:55:50Z")

</div>

Hi @JorisJoppe you were connected with the wrong demo file (other division code), I modified it in your sandbox.

Can I help you think along to how you could currently fix this?

(the `bot_name` is just adding it as a parameter, should be straightforward 🙂)