Skip to main content
POST
/
v1
/
users
/
profile
Fetch User
curl --request POST \
  --url https://dev.api.mufi.app/v1/users/profile \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "email": "jsmith@example.com",
  "referenceId": "<string>"
}'
{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "firstName": "<string>",
  "lastName": "<string>",
  "email": "jsmith@example.com",
  "referenceId": "<string>",
  "isActivated": true,
  "activatedOn": "2023-11-07T05:31:56Z",
  "wallets": [
    {
      "id": "<string>",
      "type": "Polkadot",
      "address": "<string>",
      "custody": "user-controlled"
    }
  ]
}

Authorizations

​
x-api-key
string
header
required

The API Key you were given in the developer portal. API keys are associated with your organization's project application and can have read or write permissions and an optional expiration date.

Body

application/json

This POST endpoint allows querying a user by email, id, or referenceId. Use only one field per request. If multiple fields are provided, the priority is email, followed by referenceId, and then id.

​
id
string<uuid>
​
email
string<email>
​
referenceId
string

Response

A successful response includes the user details and their wallets. Each wallet has a public address and a custody type, which can be custodial or non-custodial, depending on user control.

​
id
string<uuid>
required
​
isActivated
boolean
required
​
activatedOn
string<date-time> | null
required
​
wallets
object[]
required
​
firstName
string | null
​
lastName
string | null
​
email
string<email>
​
referenceId
string | null
⌘I