# How to get staking info by core api?

**URL:** <https://radixtalk.com/t/how-to-get-staking-info-by-core-api/1279>\
**Category:** Staking\
**Created:** [15 June 2022 06:49 UTC](https://radixtalk.com/t/how-to-get-staking-info-by-core-api/1279 "2022-06-15T06:49:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![abel](https://radixtalk.com/user_avatar/radixtalk.com/abel/32/342_2.png) [@abel](https://radixtalk.com/u/abel)\
**Post date:** [15 June 2022 06:49 UTC](https://radixtalk.com/t/how-to-get-staking-info-by-core-api/1279/1 "2022-06-15T06:49:57Z")

</div>

![image](https://radixtalk.com/uploads/default/original/1X/ad55ee03c18d66d4f6bff1bc210ced8212db83f4.png)

is there any way to get staking info, find any tx flow of staking

---

<div class="post-metadata">

**Author:** ![Faraz](https://radixtalk.com/user_avatar/radixtalk.com/faraz/32/334_2.png) [@Faraz](https://radixtalk.com/u/Faraz)\
**Post date:** [15 June 2022 11:15 UTC](https://radixtalk.com/t/how-to-get-staking-info-by-core-api/1279/3 "2022-06-15T11:15:25Z")

</div>

It’s no longer possible in the core, but you can retrieve validator stakes from the Gateway using the validator/stakes end point, or for an individual staker using the account/stakes end point:

[Gateway API Specs](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/radixdlt/radixdlt-network-gateway/1.1.1/gateway-api-spec.yaml#tag/Account/paths/~1account~1stakes/post)

---

<div class="post-metadata">

**Author:** ![abel](https://radixtalk.com/user_avatar/radixtalk.com/abel/32/342_2.png) [@abel](https://radixtalk.com/u/abel)\
**Post date:** [21 June 2022 03:07 UTC](https://radixtalk.com/t/how-to-get-staking-info-by-core-api/1279/4 "2022-06-21T03:07:53Z")

</div>

I want to calculate the APY, use this formula

```auto
APY = 100* ((ValueNow - ValueOld)/ValueOld * 365.25 * 24 * 3600) / (TimestampNow - TimestampOld)

```

but there may be some questions, if I unStaking or staked some XRD, the APY will not correct when I change the staked amount some time, is there any way to ensure the APY accurate