> ## Documentation Index > Fetch the complete documentation index at: https://docs.didit.me/llms.txt > Use this file to discover all available pages before exploring further. # Kepemilikan Dompet API: Buat Sesi Widget Bukti Kendali > Buat sesi widget Didit untuk membuktikan kepemilikan dompet kripto: tanda tangan pesan, tes Satoshi, tangkapan layar, atau deklarasi mandiri. Prompt API Sesi Widget Kepemilikan Dompet Mint Salin prompt ke papan klip \

\`Mint a hosted wallet-ownership widget session so a customer can prove control of a crypto wallet - to advance a Travel Rule transfer out of UNCONFIRMED_OWNERSHIP, or to pre-verify a wallet before any transfer exists.

Endpoint:
POST https://verification.didit.me/v3/travel-rule/widget-session/

Authentication:
Use the x-api-key header with my Didit API key.

You rarely need this call: with auto_wallet_verification on (the default), Didit auto-mints a widget session at transaction creation whenever a transfer needs end-user proof, and returns it in the transaction's action_required block. Mint manually for pre-verification or when auto_wallet_verification is off.

Request body (application/json):
\{
"wallet_address": "0x8ba1f109551bD432803012645Ac136ddd64DBA72",   // the wallet to verify
"chain": "ETH",                               // chain identifier (ETH, BTC, SOL, TRX, ...); use the same token your transfers carry
"holder_name": "Ana Diaz",                    // used for the beneficiary name match
"vendor_data": "user-042",                    // your internal id, carried onto the address-book entry
"transaction_id": "", // optional: transfer to advance when the proof verifies
"satoshi_deposit_address": "",                // optional: a deposit address you control - enables the SATOSHI_TEST method
"callback_url": "https://yourapp.example/wallet-verified",  // optional: where the widget returns the customer
"expires_in_minutes": 60                      // optional; auto-extended to cover the Satoshi test window
}

When the customer starts a proof, Didit saves the wallet to your address book with this chain (or reuses the entry with the same address and chain).
Address-book matching is chain-scoped and does not translate names ("ethereum" does not match "ETH"), so pass the same chain token your transfers carry.

What to read from the response:
\- url - send your customer there, verbatim (never construct it yourself). Open it in a real browser or the SDK modal - NEVER an embedded mobile webview (wallet deep links cannot escape a webview).
\- widget_session_id, token, expires_at.

Proof methods offered (depending on settings and mint parameters):
\- MESSAGE_SIGNING - when chain is an EVM, Solana, Bitcoin or Tron chain.
Signing works with wallets installed in the customer's browser, discovered in the page (EIP-6963 / Wallet Standard).
Pairing a mobile wallet app (for example by scanning a QR code) is not available in production today.
\- SATOSHI_TEST - a micro-deposit, offered when you pass satoshi_deposit_address and chain is an EVM, Solana or Bitcoin chain.
\- SCREENSHOT - if allow_screenshot_proof.
\- SELF_DECLARATION - if allow_self_declaration.

Detect completion:
\- Poll GET /v3/travel-rule/widget/{token}/ (completed_at becomes non-null), or
\- Subscribe to travel_rule.status.updated webhooks when the session is linked to a transfer.

Failure modes:
\- 400 - callback_url is not an absolute http(s) URL ({"callback_url": ["callback_url must be an absolute http(s) URL."]}), expires_in_minutes is outside 5 to 10080, transaction_id is not a UUID, or a field is longer than its limit.
\- 404 - transaction_id does not name a Travel Rule transfer in this application.
\- Minting does not check wallet_address against the linked transfer, but every proof on a linked session must use the transfer's counterparty wallet, otherwise starting the proof returns 400.

Full guide: /transaction-monitoring/wallet-ownership-widget.`

\
Tempel ke ## OpenAPI ````yaml id/openapi-25.json POST /v3/travel-rule/widget-session/ openapi: 3.0.0 info: version: 3.0.0 title: Didit Verification API description: API Verifikasi Identitas. Lakukan autentikasi dengan header x-api-key. servers: - url: https://verification.didit.me security: [] tags: [] paths: /v3/travel-rule/widget-session/: post: tags: - Travel Rule summary: Buat sesi widget kepemilikan dompet description: >- Buat URL/token widget kepemilikan dompet yang di-hosting. Arahkan pelanggan ke url yang dikembalikan untuk membuktikan kontrol atas dompet (penandatanganan pesan, uji Satoshi, tangkapan layar, atau deklarasi mandiri). Widget ini hanya untuk web pada rilis ini - buka url di browser sistem atau tab kustom, jangan pernah di dalam webview SDK seluler. operationId: createTravelRuleWidgetSession requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/TravelRuleWidgetSessionCreate' example: wallet_address: '0xd3b62acb76fb27a7f8961ec40fa11746b113aca9' chain: ETH holder_name: Jane Doe vendor_data: user-042 transaction_id: 99999999-aaaa-bbbb-cccc-dddddddddddd expires_in_minutes: 60 responses: '201': description: Sesi widget yang diterbitkan. content: application/json: schema: $ref: '#/components/schemas/TravelRuleWidgetSessionResponse' '400': description: >- Body tidak valid: `callback_url` bukan URL http(s) absolut, `expires_in_minutes` berada di luar rentang 5 hingga 10080, `transaction_id` bukan UUID, atau kolom melebihi batas panjangnya. content: application/json: examples: Invalid callback_url: value: callback_url: - callback_url must be an absolute http(s) URL. '404': description: >- `transaction_id` tidak merujuk pada transfer Travel Rule di dalam aplikasi ini. security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl source: >- curl -X POST https://verification.didit.me/v3/travel-rule/widget-session/ \ -H 'x-api-key: YOUR_API_KEY' -H 'Content-Type: application/json' \ -d '{"wallet_address":"0xd3b62acb76fb27a7f8961ec40fa11746b113aca9","chain":"ETH","holder_name":"Jane Doe","transaction_id":"99999999-aaaa-bbbb-cccc-dddddddddddd"}' - lang: python label: Python source: |- from didit import Didit # Reads DIDIT_API_KEY. client = Didit() result = client.travel_rule.create_widget_session( wallet_address="0xd3b62acb76fb27a7f8961ec40fa11746b113aca9", chain="ETH", holder_name="Jane Doe", vendor_data="user-042", transaction_id="99999999-aaaa-bbbb-cccc-dddddddddddd", expires_in_minutes=60, ) print(result) - lang: javascript label: Node.js source: |- import Didit from "@didit-protocol/sdk-node"; // Reads DIDIT_API_KEY. const didit = new Didit(); const result = await didit.travelRule.createWidgetSession({ wallet_address: "0xd3b62acb76fb27a7f8961ec40fa11746b113aca9", chain: "ETH", holder_name: "Jane Doe", vendor_data: "user-042", transaction_id: "99999999-aaaa-bbbb-cccc-dddddddddddd", expires_in_minutes: 60, }); console.log(result); - lang: go label: Go source: "ctx := context.Background()\n// Reads DIDIT_API_KEY.\nclient := didit.NewClient()\n\nresult, err := client.TravelRule.CreateWidgetSession(ctx, didit.TravelRuleWidgetSessionCreate{\n\tWalletAddress: didit.String(\"0xd3b62acb76fb27a7f8961ec40fa11746b113aca9\"),\n\tChain: didit.String(\"ETH\"),\n\tHolderName: didit.String(\"Jane Doe\"),\n\tVendorData: didit.String(\"user-042\"),\n\tTransactionID: didit.String(\"99999999-aaaa-bbbb-cccc-dddddddddddd\"),\n\tExpiresInMinutes: didit.Int(60),\n})\nif err != nil {\n\tlog.Fatal(err)\n}\nfmt.Printf(\"%+v\\n\", result)" - lang: java label: Java source: >- import me.didit.Didit; import me.didit.types.TravelRuleWidgetSessionCreate; // Reads DIDIT_API_KEY. Didit client = new Didit(); var result = client.travelRule().createWidgetSession(TravelRuleWidgetSessionCreate.builder() .walletAddress("0xd3b62acb76fb27a7f8961ec40fa11746b113aca9") .chain("ETH") .holderName("Jane Doe") .vendorData("user-042") .transactionId("99999999-aaaa-bbbb-cccc-dddddddddddd") .expiresInMinutes(60L) .build()); System.out.println(result); - lang: php label: PHP source: |- travelRule->createWidgetSession([ 'wallet_address' => '0xd3b62acb76fb27a7f8961ec40fa11746b113aca9', 'chain' => 'ETH', 'holder_name' => 'Jane Doe', 'vendor_data' => 'user-042', 'transaction_id' => '99999999-aaaa-bbbb-cccc-dddddddddddd', 'expires_in_minutes' => 60, ]); print_r($result->toArray()); - lang: ruby label: Ruby source: |- require "didit" # Reads DIDIT_API_KEY. didit = Didit::Client.new result = didit.travel_rule.create_widget_session( wallet_address: "0xd3b62acb76fb27a7f8961ec40fa11746b113aca9", chain: "ETH", holder_name: "Jane Doe", vendor_data: "user-042", transaction_id: "99999999-aaaa-bbbb-cccc-dddddddddddd", expires_in_minutes: 60 ) puts result.to_h - lang: csharp label: .NET source: >- using System; using System.Text.Json; using Didit; // Reads DIDIT_API_KEY. using var client = new DiditClient(); var result = await client.TravelRule.CreateWidgetSessionAsync(new TravelRuleWidgetSessionCreate { WalletAddress = "0xd3b62acb76fb27a7f8961ec40fa11746b113aca9", Chain = "ETH", HolderName = "Jane Doe", VendorData = "user-042", TransactionId = "99999999-aaaa-bbbb-cccc-dddddddddddd", ExpiresInMinutes = 60, }); Console.WriteLine(JsonSerializer.Serialize(result)); components: schemas: TravelRuleWidgetSessionCreate: type: object properties: wallet_address: type: string description: >- Alamat dompet yang akan diverifikasi. Opsional; jika kosong, alamat harus diberikan saat proses pembuktian dimulai. maxLength: 128 chain: type: string description: >- Token chain untuk alamat, misalnya `ETH`, `BTC`, atau `SOL`. Gunakan token yang sama seperti di buku alamat dompet Anda. Penandatanganan pesan dan pengujian Satoshi hanya ditawarkan untuk chain yang didukung. Entri buku alamat yang diverifikasi oleh bukti menyimpannya di bawah pengidentifikasi kanonisnya (ETH, BTC, SOL, TRX). maxLength: 32 holder_name: type: string description: Nama pemegang dompet, digunakan untuk pencocokan nama penerima. maxLength: 255 vendor_data: type: string description: >- Pengenal internal Anda untuk pemegang, diteruskan ke entri buku alamat yang dibuat. maxLength: 255 transaction_id: type: string format: uuid description: >- Opsional. UUID transaksi Didit dari transfer Travel Rule yang akan dilanjutkan saat bukti terverifikasi. nullable: true satoshi_deposit_address: type: string description: >- Opsional. Alamat deposit yang Anda kendalikan; menyediakannya akan mengaktifkan metode pembuktian SATOSHI_TEST. maxLength: 128 callback_url: type: string description: >- Opsional. URL http(s) absolut tempat widget mengembalikan pelanggan setelah selesai. maxLength: 512 expires_in_minutes: type: integer description: >- Opsional. Masa berlaku tautan yang dibuat, dalam hitungan menit. Diperpanjang secara otomatis untuk mencakup jendela uji Satoshi saat SATOSHI_TEST ditawarkan. default: 60 minimum: 5 maximum: 10080 TravelRuleWidgetSessionResponse: type: object properties: widget_session_id: type: string format: uuid token: type: string description: Token sesi opaque yang disematkan dalam URL widget. url: type: string description: >- URL widget kepemilikan dompet yang di-hosting. Buka secara persis di browser sistem (jangan pernah di dalam webview SDK seluler). expires_at: type: string format: date-time securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- Kunci API aplikasi Anda, dari Developers -> API keys di Business Console. Kunci utama memiliki akses penuh. Kunci bernama dapat diberi cakupan: none, read, atau write per sumber daya, dibatasi pada beberapa alur kerja atau pada sesi yang disetujui, pada daftar alamat IP, dan pada tanggal kedaluwarsa. 401 berarti kuncinya salah, dicabut, atau kedaluwarsa; 403 berarti tidak ada kunci yang dikirimkan, kunci tidak memiliki akses ke sumber daya atau tindakan ini, atau permintaan datang dari alamat di luar daftar IP-nya; 404 pada rute sesi berarti sesi berada di luar alur kerja atau status kunci tersebut. Kunci tanpa akses media menerima URL gambar, video, dan PDF sebagai null, dan kunci tanpa izin tulis sesi menerima tautan sesi dan token sebagai null. Lihat https://docs.didit.me/console/api-keys. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.