> ## Documentation Index > Fetch the complete documentation index at: https://developer.finogates.com/llms.txt > Use this file to discover all available pages before exploring further. # Create Digital Asset Wallet > Create a digital asset wallet (a deposit address) for one of your users — or get the existing one back if it was already created. Every new asset-and-network combination must first be approved by Finogate's team. When you ask for a new one, this returns straight away with a request ID and a "waiting for approval" status. Once the team approves it, the wallet is created for you automatically — you do not need to call this again. If you ask for a wallet that already exists, its deposit address is returned right away. Some assets also need a small amount of a separate "gas" asset to cover network fees. When that applies, the response includes a ``gas_dependency`` section so you can prompt the user to top it up. **Warning: sending a digital asset on the wrong network is usually lost for good.** The response gives you both the deposit ``address`` and its ``network_code`` (such as ``ethereum`` or ``tron``). Users must send funds on the exact network the address belongs to. Sending an asset from a different blockchain — for example USDT on Tron to an Ethereum address, or Bitcoin to an Ethereum-style address — loses the money for good, because it never reaches us and cannot be recovered. Always show the network clearly on any deposit screen you build. ## OpenAPI ````yaml POST /v1/platform/digital-assets/wallets openapi: 3.1.0 info: title: Finogate Platform API v1 version: 0.1.0 servers: - url: https://api-sandbox.finogates.com description: Sandbox - url: https://api.finogates.com description: Production security: [] tags: - name: auth - name: users - name: payees - name: verification - name: bank accounts - name: card processing - name: digital-assets - name: international - name: onboarding - name: pending-applications - name: wallets - name: payments - name: catalog - name: webhooks - name: phone-numbers - name: sms - name: calls - name: listings - name: embed-tokens paths: /v1/platform/digital-assets/wallets: post: tags: - digital-assets summary: Create a Digital Asset Wallet description: |- Create a digital asset wallet (a deposit address) for one of your users — or get the existing one back if it was already created. Every new asset-and-network combination must first be approved by Finogate's team. When you ask for a new one, this returns straight away with a request ID and a "waiting for approval" status. Once the team approves it, the wallet is created for you automatically — you do not need to call this again. If you ask for a wallet that already exists, its deposit address is returned right away. Some assets also need a small amount of a separate "gas" asset to cover network fees. When that applies, the response includes a ``gas_dependency`` section so you can prompt the user to top it up. **Warning: sending a digital asset on the wrong network is usually lost for good.** The response gives you both the deposit ``address`` and its ``network_code`` (such as ``ethereum`` or ``tron``). Users must send funds on the exact network the address belongs to. Sending an asset from a different blockchain — for example USDT on Tron to an Ethereum address, or Bitcoin to an Ethereum-style address — loses the money for good, because it never reaches us and cannot be recovered. Always show the network clearly on any deposit screen you build. operationId: create_wallet_v1_platform_digital_assets_wallets_post requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/CryptoWalletCreate' responses: '201': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/CommonResponse' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - _AuthenticatedBearer: [] components: schemas: CryptoWalletCreate: properties: user_id: type: string format: uuid title: User Id description: End-user public UUID under the authenticated platform. asset_code: type: string maxLength: 50 minLength: 1 title: Asset Code description: Catalog asset code, e.g. ``usdt``, ``btc``, ``eth``. examples: - usdt network_code: type: string maxLength: 50 minLength: 1 title: Network Code description: Catalog network code, e.g. ``ethereum``, ``tron``, ``bitcoin``. examples: - tron type: object required: - user_id - asset_code - network_code title: CryptoWalletCreate description: Request body for ``POST /platform/digital-assets/wallets``. CommonResponse: properties: status_code: type: integer title: Status Code description: HTTP status code for the response. data: title: Data description: Payload or error details. query_generated_time: type: integer title: Query Generated Time description: >- UTC timestamp (milliseconds since epoch) when response was generated. type: object required: - status_code - data - query_generated_time title: CommonResponse description: |- Standard response wrapper for single-object responses and errors. Generic over the payload type. A route that declares ``CommonResponse[SomeModel]`` gets the real ``data`` schema rendered in OpenAPI/Swagger; a bare ``CommonResponse`` leaves ``data`` untyped. HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: _AuthenticatedBearer: type: oauth2 flows: password: scopes: {} tokenUrl: /v1/platform/auth/token ````