Create account (deprecated)
curl --request POST \
--url https://api.example.com/api/v1/user/accountsconst options = {method: 'POST'};
fetch('https://api.example.com/api/v1/user/accounts', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.example.com/api/v1/user/accounts"
response = requests.post(url)
print(response.text)Account Management
Create account (deprecated)
Formerly opened a new Qash account for the authenticated user. Accounts are now provisioned automatically.
POST
/
api
/
v1
/
user
/
accounts
Create account (deprecated)
curl --request POST \
--url https://api.example.com/api/v1/user/accountsconst options = {method: 'POST'};
fetch('https://api.example.com/api/v1/user/accounts', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.example.com/api/v1/user/accounts"
response = requests.post(url)
print(response.text)Deprecated — do not call this endpoint. Every user gets a USDC account automatically the first time they log in — it’s a side effect of wallet provisioning, not a step you trigger. There is no manual account-creation step in the current flow.Call List accounts after login to retrieve the account
id for deposits, transfers, and transaction history. See the Partner Integration Guide for the full current flow.Why this changed
Earlier versions of the integration required an explicitPOST /api/v1/user/accounts call before a user could hold funds, and supported creating accounts in arbitrary currencies. Today, QASH only supports a single USDC account per user, so there is nothing left to configure — the account is created automatically, with the correct currency and type, the moment the user’s wallet is provisioned at login. Removing the manual step also removes an entire class of integration bugs: wrong currency, wrong account type, or accounts left uncreated.
Original reference (archived)
POST /api/v1/user/accounts
Authorization: Bearer <user-access-token>
Content-Type: application/json
{
"description": "Main Account",
"asset": "USDC",
"type": "LIABILITY"
}
{
"id": 619,
"description": "Main Account",
"asset": "USDC",
"type": "LIABILITY",
"balance": 0
}