> ## 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. # Import Wallet Addresses > Add up to 10,000 wallets to your Travel Rule address book in one call, as JSON or as a CSV file. A wallet can be sent by its address, by the SHA-256 of its lowercased address (`address_hash`) to keep the address private, or both. The import is idempotent: a wallet already in the book is reported as `existing` and left untouched, so the same file can be sent again. Each row is validated on its own, so one bad row never fails the others. A wallet imported by its hash only matches transfers to that address and can be proven with the wallet-ownership widget like any other entry. Import Wallet Addresses API Prompt Copy prompt to clipboard \

\`Import many wallets into the application's Travel Rule address book in one call, as JSON or as a CSV file.

Endpoint:
POST https://verification.didit.me/v3/travel-rule/wallet-addresses/import/

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

Request body, one of:
\- application/json: {"entries": [row, ...]} or a bare JSON array of rows.
\- multipart/form-data: a "file" field holding a UTF-8 CSV of at most 5 MB with a header row naming the columns.
At most 10,000 rows either way.

Row fields (every one optional, but each row needs address, address_hash or both):
\{
"address": "0xBeneficiaryWallet01",      // the wallet address (alias: walletAddress)
"address_hash": "4f7d...3f2e",           // SHA-256 of the lowercased address, 64 hex or 44 base64 characters (alias: walletAddressHash)
"chain": "ETH",
"memo": "104729",                        // destination tag or memo on XRP, XLM, EOS, ATOM, HBAR (alias: destinationTag)
"holder_name": "Ana Diaz",
"holder_vendor_data": "user-042",        // your id for the holder (alias: externalUserId)
"entity_type": "individual",             // individual or company
"label": "Main deposit wallet",
"owner_type": "customer",                // customer, internal or vasp
"travel_address": "ta...",
"self_declared": false                   // only when your settings allow self-declaration
}

Behavior:
\- Send address_hash alone to register a wallet without disclosing its address. Sent with address, it must be that address's hash.
\- Idempotent: a wallet already in the book (same address or hash, chain and memo) is reported as "existing" and left untouched, so the same file can be sent again.
\- A row that repeats an earlier row of the same import is "duplicate" and names that row.
\- Each row is validated on its own, so one bad row never fails the others.
\- An entry imported by its hash only matches transfers to that address, and can be proven with the wallet-ownership widget like any other entry.
\- In a CSV, an empty cell counts as not sent and columns the import does not read are ignored.

What to read from the response:
\- 200 when no row failed, 207 when at least one did.
\- total, created, existing, duplicate, failed - the counts.
\- rows[] - one result per row in the order sent: row (from 1), status, entry_id, errors, duplicate_of_row.

Failure modes:
\- 400 - both entries and a file, or neither; more than 10,000 rows; a file over 5 MB, not UTF-8 CSV, or without a header row or rows.
\- 401 - missing or malformed x-api-key.

Full guide: /transaction-monitoring/travel-rule#importing-wallets-in-bulk.`

\
Paste into ## OpenAPI ````yaml POST /v3/travel-rule/wallet-addresses/import/ openapi: 3.0.0 info: version: 3.0.0 title: Didit Verification API description: Identity verification API. Authenticate with x-api-key header. servers: - url: https://verification.didit.me security: [] tags: [] paths: /v3/travel-rule/wallet-addresses/import/: post: tags: - Travel Rule summary: Import wallet addresses in bulk description: >- Add up to 10,000 wallets to your Travel Rule address book in one call, as JSON or as a CSV file. A wallet can be sent by its address, by the SHA-256 of its lowercased address (`address_hash`) to keep the address private, or both. The import is idempotent: a wallet already in the book is reported as `existing` and left untouched, so the same file can be sent again. Each row is validated on its own, so one bad row never fails the others. A wallet imported by its hash only matches transfers to that address and can be proven with the wallet-ownership widget like any other entry. operationId: importTravelRuleWalletAddresses requestBody: required: true content: application/json: schema: oneOf: - type: object required: - entries properties: entries: type: array minItems: 1 maxItems: 10000 items: $ref: '#/components/schemas/WalletAddressImportRow' - type: array minItems: 1 maxItems: 10000 items: $ref: '#/components/schemas/WalletAddressImportRow' example: entries: - address: 0xBeneficiaryWallet01 chain: ETH holder_name: Ana Diaz holder_vendor_data: user-042 - address_hash: >- 4f7d2e1c9b8a7f6e5d4c3b2a1f0e9d8c7b6a5f4e3d2c1b0a9f8e7d6c5b4a3f2e chain: bitcoin holder_vendor_data: user-043 - address: rExchangeSharedAddress01 chain: XRP memo: '104729' holder_name: Ana Diaz multipart/form-data: schema: type: object required: - file properties: file: type: string format: binary description: >- A UTF-8 CSV file of at most 5 MB with a header row naming its columns (the row fields or their aliases). Empty cells count as not sent; columns the import does not read are ignored. responses: '200': description: >- Every row was created, already in the book, or a repeat of an earlier row. content: application/json: schema: $ref: '#/components/schemas/WalletAddressImportReport' example: total: 3 created: 2 existing: 1 duplicate: 0 failed: 0 rows: - row: 1 status: existing entry_id: 11111111-2222-3333-4444-555555555555 errors: {} duplicate_of_row: null - row: 2 status: created entry_id: 22222222-3333-4444-5555-666666666666 errors: {} duplicate_of_row: null - row: 3 status: created entry_id: 33333333-4444-5555-6666-777777777777 errors: {} duplicate_of_row: null '207': description: >- At least one row failed; the others were imported. Each failed row names its errors. content: application/json: schema: $ref: '#/components/schemas/WalletAddressImportReport' example: total: 2 created: 1 existing: 0 duplicate: 0 failed: 1 rows: - row: 1 status: created entry_id: 44444444-5555-6666-7777-888888888888 errors: {} duplicate_of_row: null - row: 2 status: failed entry_id: null errors: address: - Send address, address_hash or both. duplicate_of_row: null '400': description: >- The request itself cannot be read: both `entries` and a `file`, or neither; more than 10,000 rows; a file over 5 MB, not UTF-8 CSV, without a header row or without rows. content: application/json: schema: type: object example: file: - At most 10000 rows per import. security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl (JSON) source: >- curl -X POST https://verification.didit.me/v3/travel-rule/wallet-addresses/import/ \ -H 'x-api-key: YOUR_API_KEY' -H 'Content-Type: application/json' \ -d '{"entries": [{"address": "0xBeneficiaryWallet01", "chain": "ETH", "holder_name": "Ana Diaz"}, {"address": "rExchangeSharedAddress01", "chain": "XRP", "memo": "104729"}]}' - lang: curl label: curl (CSV) source: >- curl -X POST https://verification.didit.me/v3/travel-rule/wallet-addresses/import/ \ -H 'x-api-key: YOUR_API_KEY' \ -F 'file=@wallets.csv;type=text/csv' components: schemas: WalletAddressImportRow: type: object description: >- One wallet to import: by its `address`, its `address_hash`, or both. The camelCase forms of these fields are accepted too, as are `walletAddress`, `walletAddressHash`, `destinationTag` and `externalUserId`. properties: address: type: string maxLength: 128 description: 'The wallet address. Alias: `walletAddress`.' address_hash: type: string description: >- SHA-256 of the lowercased address, as 64 hex characters or 44 base64 characters. Send it alone to register a wallet without disclosing its address; sent with `address`, it must be that address's hash. Alias: `walletAddressHash`. chain: type: string maxLength: 32 memo: type: string maxLength: 256 description: >- The destination tag or memo. XRP: a destination tag, a whole number from 0 to 4294967295 (a JSON number is accepted). XLM: a text memo of up to 28 bytes, a 64-bit id or a 32-byte hash in hex. EOS: up to 256 bytes. ATOM: up to 256 characters. HBAR: up to 100 bytes. Bitcoin, EVM, Solana, Tron, Litecoin, Bitcoin Cash, Dogecoin and Lightning wallets take no memo: one there is a `400`. holder_name: type: string maxLength: 255 holder_vendor_data: type: string maxLength: 255 description: 'Your internal identifier for the holder. Alias: `externalUserId`.' entity_type: type: string enum: - individual - company default: individual label: type: string maxLength: 255 owner_type: type: string enum: - customer - internal - vasp default: customer travel_address: type: string maxLength: 512 self_declared: type: boolean default: false description: >- Create the entry already verified through a self-declaration, when your settings allow it. WalletAddressImportReport: type: object description: What happened to each row of an import, in the order sent. properties: total: type: integer created: type: integer existing: type: integer duplicate: type: integer failed: type: integer rows: type: array items: type: object properties: row: type: integer description: The row's number, from 1. status: type: string enum: - created - existing - duplicate - failed description: >- `created`: added to the book. `existing`: the wallet is already in the book and was left untouched. `duplicate`: repeats an earlier row of this import. `failed`: see `errors`. entry_id: type: string format: uuid nullable: true description: The address-book entry the row created or found. errors: type: object description: Field errors of a `failed` row; empty otherwise. duplicate_of_row: type: integer nullable: true description: On a `duplicate` row, the row it repeats. securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is missing, wrong, revoked or expired; 403 means the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.