---
title: "Get history of spend backs by user token"
method: GET
path: "/payout/spendback/{user_token}"
tags: ["Spend Back"]
---

# Get history of spend backs by user token

`GET /payout/spendback/{user_token}`

This **GET** endpoint is used to retrieve the history of spendbacks for a specific user token. <br> You can use this endpoint to help manage your payment operations and track the usage of funds by your users. <br> To use this endpoint, you need to provide the `user_token` as a parameter in the URL Path. <br> The endpoint will then return a list of all the historical spendbacks for the provided user token. The response will contain a JSON array with details for each spendback transaction.

## Headers

- `Idempotency-Key` string

## Response `200`

Succesful operation.

- SpendBacks[]
  - `spendback_token` string, required — Token representing the load token
  - `time_of_spendback` string, YYYY-MM-DDThh:mm:ss, required — The timestamp the spend back was created in the system. Using UTC timestamp.[ISO 8601](https://en.wikipedia.org/wiki/ISO_8601)
  - `client_spendback_id` string, required — A client defined spend back identifier. This is the unique ID assigned to the spend back on your system. Max 50 characters.
  - `source_token` string, uuid, required — Token that represents the funding source i.e. bank account, wallet. 36 characters long
  - `wallet_token` string, uuid, required — Token that represents the wallet that received the funds. 36 characters long
  - `amount` number, required — The amount to credit the user's wallet in source currency
  - `source_currency_code` string, required — The currency originating balance is stored in. Using [ISO 4217](https://en.wikipedia.org/wiki/ISO_4217) format. In most cases this value will be USD, and therefore the defaut value if none is provided
  - `notes` string, required — A description for the load. Will be visible to the user receiving the load
  - `metadata` object — Optional JSON object with attributes that can later be searched to locate this spendback. Do not include PII as this object is not encrypted.

## Other responses

- `400` — Bad request.
- `401` — Unauthorized.
- `403` — Forbidden.
- `404` — Not found.
- `405` — Method Not Allowed.
- `500` — Internal server error.
- `504` — Gateway Time-out.

---

[API](https://skmtc.net/masspay/apis/masspay-api.md) · [All operations](https://skmtc.net/masspay/apis/masspay-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/masspay/masspay-api/revisions/c03b61a6a551/schema)