---
title: "Get a User Profile"
method: GET
path: "/v1/user"
tags: ["User"]
---

# Get a User Profile

`GET /v1/user`

> 📘
>
> You can place the bearer `access_token` for a specific user into the Authentication section of this documentation 👉.

This endpoint retrieves the profile information for the User whose `access_token` is passed in the authorization header.

## Response `200`

Successful response

- object
  - `id` string — Unique Astra user ID
  - `email` string — Email address of the user
  - `phone` string — Phone number of the user
  - `first_name` string — First name of the user
  - `last_name` string — Last name of the user
  - `preferred_first_name` string — Preferred first name of the user
  - `preferred_last_name` string — Preferred last name of the user
  - `preferred_pronouns` string — Preferred pronouns of the user
  - `status` 'approved' | 'pending' | 'retry' | 'document' | 'suspended' | 'rejected' — Current status of the user (Details on [User Statuses](https://docs.astra.finance/reference/user-statuses))
  - `rejection_reasons` unknown[] — List of details on why a User is not approved
    - unknown
  - `kyc_type` 'receive-only' | 'unverified' | 'verified' — The verification type of the user, which determines the user's capabilities to send and/or receive funds
  - `metadata` object — An optional metadata object for submitting custom data (during User Intent creation) that will be associated with the User Intent and the User
    - `custom_field_name_1` string — Supply a custom name for any number of fields, and provide it a custom value
    - `custom_field_name_2` string — Supply a custom name for any number of fields, and provide it a custom value

## Other responses

- `401` — Unauthorized

---

[API](https://skmtc.net/astra/apis/astra-developer-api.md) · [All operations](https://skmtc.net/astra/apis/astra-developer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/astra/astra-developer-api/versions/09f0430e5d33/schema)