> For the complete documentation index, see [llms.txt](https://docs.fuul.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fuul.xyz/developer-guide/claiming-onchain-rewards/get-claim-checks.md).

# Get Claim Checks

Claim checks are signed vouchers that allow users to claim their rewards onchain. This step is the same regardless of whether you're claiming on EVM or SVM.

Use `Fuul.getClaimableChecks` from `@fuul/sdk`:

```typescript
import { Fuul } from '@fuul/sdk';

const claimChecks = await Fuul.getClaimableChecks({
  user_identifier: '0x1234...',
  user_identifier_type: 'evm_address', // or 'solana_address'
});
```

You can also call the [claim check endpoint](https://fuul.readme.io/reference/generateclaimsignature) on the Fuul API directly.

{% hint style="info" %}
`getClaimableChecks` was introduced in SDK version **7.8.0**. Upgrade if you're on an earlier version.
{% endhint %}

## Get claim totals

To show users their claimed and unclaimed balances without building a full transaction ([API reference](https://fuul.readme.io/reference/getclaimabletotals)):

```typescript
import { Fuul } from '@fuul/sdk';

const totals = await Fuul.getClaimCheckTotals({
  user_identifier: '0x1234...',
  user_identifier_type: 'evm_address', // or 'solana_address'
});
// Returns { claimed: [...], unclaimed: [...] } grouped by currency
```

## Claim check aggregation (open checks)

Some projects enable **claim check aggregation**, which batches multiple rewards into a single on-chain transaction per currency. This is optional and configured per project.

When aggregation is enabled, claim checks start with status `open` — they accumulate rewards over time without being signed yet. New rewards for the same user, currency, and reason are merged into the existing open check by summing amounts and extending deadlines. This reduces on-chain transactions from one per reward event to one per currency/reason combination.

To finalize an open check and make it claimable, call `POST /claim-checks/close`:

```typescript
import { Fuul } from '@fuul/sdk';

await Fuul.closeClaimChecks({
  user_identifier: '0x1234...',
  user_identifier_type: 'evm_address',
});
```

After closing, the check transitions from `open` to `unclaimed` and receives its signature — at which point it's returned by `getClaimableChecks` and ready to claim onchain.

{% hint style="info" %}
If aggregation is not enabled for a project, claim checks are signed immediately at creation time and are returned as `unclaimed` from the start. No `close` call is needed.
{% endhint %}

You can filter claim checks by status using the `GET /claim-checks` endpoint (`open`, `unclaimed`, or `claimed`).

## Next steps

Once you have your claim checks, follow the guide for your chain:

* [EVM Claiming](/developer-guide/claiming-onchain-rewards/evm.md) for Ethereum, Arbitrum, Base, HyperEVM, Ink, Optimism
* [SVM Claiming (Solana)](/developer-guide/claiming-onchain-rewards/svm-solana.md) — for Solana Mainnet, Devnet, Fogo Mainnet


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fuul.xyz/developer-guide/claiming-onchain-rewards/get-claim-checks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.