---
title: "List addresses for profile"
method: GET
path: "/api/v1/addresses/{reference}"
tags: ["addresses"]
---

# List addresses for profile

`GET /api/v1/addresses/{reference}`

List addresses for a profile by reference with pagination.

## Path parameters

- `reference` string, required

## Query parameters

- `skip` number
- `take` number

## Headers

- `x-sdk-version` string, required

## Response `200`

Addresses for profile (paginated)

- GetAddressListResponseBodyDTO
  - `data` AddressDataDTO[], required
    - `id` string, uuid, required
    - `address` string, required — On-chain address string
    - `reference` string, required — Profile reference that owns this address
    - `networkId` string, uuid — Network UUID
    - `date` string, date-time, required — Address creation timestamp
    - `label` string — Optional human-readable label
    - `sub` string, required — Organization subject identifier
    - `balance` string, required — Native balance as a decimal string (wei / satoshi)
    - `miniWalletId` string, uuid, required — Parent wallet UUID
  - `pagination` AddressListPaginationDto, required
    - `totalElements` number, required — Total number of items
    - `totalPages` number, required — Total number of pages
    - `skip` number, required
    - `take` number, required

## Other responses

- `400` — Bad request or validation failed. **Applicable error codes and client messages** The response body contains one of the following error codes and the corresponding client-facing message. | Code | Client message | |------|----------------| | ERR-010 | The request could not be processed. | | ERR-022 | Invalid pagination parameters. |
- `401` — Unauthorized – invalid or missing token. **Applicable error codes and client messages** The response body contains one of the following error codes and the corresponding client-facing message. | Code | Client message | |------|----------------| | ERR-008 | You need to sign in to continue. | | ERR-011 | Your session is invalid or expired. Please sign in again. |
- `403` — Forbidden – insufficient permissions. **Applicable error codes and client messages** The response body contains one of the following error codes and the corresponding client-facing message. | Code | Client message | |------|----------------| | ERR-009 | You don't have permission to do that. | | ERR-410 | Error occurred |
- `404` — Resource not found. **Applicable error codes and client messages** The response body contains one of the following error codes and the corresponding client-facing message. | Code | Client message | |------|----------------| | ERR-006 | The requested resource was not found. |
- `500` — Internal server error. **Applicable error codes and client messages** The response body contains one of the following error codes and the corresponding client-facing message. | Code | Client message | |------|----------------| | ERR-019 | Something went wrong on our side. | | ERR-999 | An unexpected error occurred. Please try again. |

## Changes

- **2026-04-21** `bdac7e47d1c2` — 1 breaking, 35 warning
  - removed the required property `data/items/path` from the response with the `200` status
  - added the new `ERR_147` enum value to the `allOf[#/components/schemas/ApiErrorResponseDto]/code` response property for the response status `400`
  - added the new `ERR_147` enum value to the `allOf[#/components/schemas/ApiErrorResponseDto]/code` response property for the response status `401`
  - added the new `ERR_147` enum value to the `allOf[#/components/schemas/ApiErrorResponseDto]/code` response property for the response status `403`
  - …32 more
- **2026-03-13** `86f37d72f0a0` — 41 breaking, 20 warning, 24 info
  - the `header` request parameter `x-sdk-version` became required
  - the response's body type/format changed from `object`/`` to ``/`` for status `400`
  - the response's body type/format changed from `object`/`` to ``/`` for status `401`
  - the response's body type/format changed from `object`/`` to ``/`` for status `403`
  - …81 more
- **2026-01-31** `13aade479509` — 1 breaking, 9 info
  - the response's body type/format changed from ``/`` to `object`/`` for status `200`
  - api operation id `getProfileAddresses` removed and replaced with `getAddressForProfile`
  - removed `#/components/schemas/SuccessResponse, subschema #2` from the response body `allOf` list for the response status `200`
  - added the non-success response with the status `400`
  - …6 more

[Change history](https://skmtc.dev/oumla/apis/oumla-core-server/changes/api/v1/addresses/:reference/get.md)

---

[API](https://skmtc.dev/oumla/apis/oumla-core-server.md) · [All operations](https://skmtc.dev/oumla/apis/oumla-core-server/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/oumla/oumla-core-server/revisions/2154835230b5/schema)