> ## 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.
# Approve or Reject a Screenshot Wallet Proof API
> Approve or reject a screenshot wallet-ownership proof from your review queue. Approval verifies the wallet and applies the ownership to the linked transfer.
Decide Wallet Proof API Prompt
Copy prompt to clipboard
\`Approve or reject a screenshot wallet-ownership proof from my review queue.
Endpoint:
POST [https://verification.didit.me/v3/travel-rule/wallet-proofs/\{proof\_uuid}/decision/](https://verification.didit.me/v3/travel-rule/wallet-proofs/\{proof_uuid}/decision/)
Authentication:
Use the x-api-key header with my Didit API key.
Body:
* decision - "approve" or "reject".
* note - optional, up to 512 characters, kept with the proof and returned as review\_note.
Behavior:
* approve verifies the proof and the wallet address book entry, and applies the ownership to the transfer the widget session was minted for, exactly as a verified signature does.
* A screenshot never confirms a transfer another Didit customer sent over the INTERNAL rail: that needs a signed message or a test deposit.
* reject closes the proof as REJECTED with failure\_reason REVIEW\_REJECTED. It uses one of the widget session's attempts; the end user can start a new proof from the widget while attempts remain. Your note is never shown to the end user.
* Returns the decided proof, in the same shape as the review queue.
Failure modes:
* 404 - no submitted screenshot proof with this id in my application.
* 409 - already decided (the body carries its status), or code OWNERSHIP\_CHANGED when the wallet's holder changed or the wallet was deleted after the widget session was minted; ask the current holder for a new proof.
* 400 - invalid decision or a note that is too long.
* 401 - missing or malformed x-api-key.
Full guide: /transaction-monitoring/wallet-ownership-widget#what-it-proves.\`
Paste into
## OpenAPI
````yaml POST /v3/travel-rule/wallet-proofs/{proof_uuid}/decision/
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-proofs/{proof_uuid}/decision/:
post:
tags:
- Travel Rule
summary: Approve or reject a screenshot wallet proof
description: >-
Decide a screenshot proof from your review queue. approve verifies the
proof and the address book entry and applies the ownership to the
transfer the widget session was minted for, exactly as a verified
signature does. A screenshot never confirms a transfer that another
Didit customer sent over the INTERNAL rail: that takes a signed message
or a test deposit. reject closes the proof as REJECTED with
failure_reason REVIEW_REJECTED; the end user can start a new proof from
the widget. The note is kept with the proof.
operationId: decideTravelRuleWalletProof
parameters:
- name: proof_uuid
in: path
required: true
description: proof_id from the review queue.
schema:
type: string
format: uuid
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/TravelRuleWalletProofDecision'
responses:
'200':
description: The decided proof.
content:
application/json:
schema:
$ref: '#/components/schemas/TravelRuleWalletProofReview'
'400':
description: Invalid decision, or a note longer than 512 characters.
'401':
description: Missing or invalid x-api-key.
'403':
description: The caller lacks the transactions permission.
'404':
description: No submitted screenshot proof with this id in your application.
'409':
description: >-
The proof is already decided (the body carries its status), or code
OWNERSHIP_CHANGED: the wallet's holder changed or the wallet was
deleted after the widget session was minted, so the proof is closed
and the current holder needs a new one.
content:
application/json:
schema:
$ref: '#/components/schemas/TravelRuleWidgetProofError'
security:
- ApiKeyAuth: []
x-codeSamples:
- lang: curl
label: curl
source: >-
curl -X POST
https://verification.didit.me/v3/travel-rule/wallet-proofs/{proof_uuid}/decision/
\
-H 'x-api-key: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"decision": "approve", "note": "Address matches the wallet app."}'
components:
schemas:
TravelRuleWalletProofDecision:
type: object
required:
- decision
properties:
decision:
type: string
enum:
- approve
- reject
note:
type: string
maxLength: 512
description: Optional. Kept with the proof and returned as review_note.
TravelRuleWalletProofReview:
type: object
properties:
proof_id:
type: string
format: uuid
method:
type: string
enum:
- SCREENSHOT
status:
type: string
enum:
- PENDING
- VERIFIED
- REJECTED
- EXPIRED
wallet_address:
type: string
chain:
type: string
description: Canonical chain identifier, e.g. ETH, BTC, SOL, TRX.
holder_name:
type: string
is_ownership_verified:
type: boolean
description: >-
Whether the address book entry is ownership-verified, by this proof
or another one.
transaction_id:
type: string
format: uuid
nullable: true
description: >-
The transaction whose Travel Rule transfer the widget session was
minted for. Null for a session minted without a transaction_id.
file_name:
type: string
nullable: true
content_type:
type: string
nullable: true
screenshot_url:
type: string
nullable: true
description: >-
Time-limited link to the uploaded screenshot. List the queue again
for a fresh link.
attempts:
type: integer
description: How many files the end user uploaded for this proof.
failure_reason:
allOf:
- $ref: '#/components/schemas/TravelRuleWalletProofFailureReason'
description: >-
REVIEW_REJECTED after a rejection, OWNERSHIP_CHANGED when the wallet
changed holder or was deleted before a decision. Empty otherwise.
method_chosen_at:
type: string
format: date-time
nullable: true
description: When the end user picked the screenshot method.
decided_at:
type: string
format: date-time
nullable: true
decided_by:
type: string
description: >-
Who closed the proof: review: for a console
reviewer, review for an API-key decision, widget or sweeper when
Didit closed it automatically. Empty while PENDING.
review_note:
type: string
description: The note sent with the decision. Empty when none.
created_at:
type: string
format: date-time
TravelRuleWidgetProofError:
type: object
properties:
detail:
type: string
description: Human-readable message in English.
code:
allOf:
- $ref: '#/components/schemas/TravelRuleWalletProofFailureReason'
description: >-
Machine-readable reason, so a client can show its own translated
message.
status:
type: string
enum:
- PENDING
- VERIFIED
- REJECTED
- EXPIRED
description: >-
Present when the proof is closed: REJECTED by the deposit just
submitted (400), or REJECTED or EXPIRED when evidence is sent to a
proof that is already closed (409).
proof_id:
type: string
format: uuid
description: 'Present with status: the closed proof.'
method:
type: string
enum:
- MESSAGE_SIGNING
- SATOSHI_TEST
- SCREENSHOT
- SELF_DECLARATION
description: 'Present with status: the closed proof''s method.'
max_attempts:
type: integer
description: 'Present with status: rejected wallet proofs this session allows.'
attempts_used:
type: integer
description: 'Present with status: rejected proofs so far.'
attempts_remaining:
type: integer
description: >-
Present with status: when 0, starting another proof answers 409 and
you mint a new widget session.
TravelRuleWalletProofFailureReason:
type: string
enum:
- ''
- SIGNATURE_INVALID
- SIGNATURE_UNSUPPORTED_SCHEME
- DEPOSIT_NOT_FOUND
- DEPOSIT_UNCONFIRMED
- DEPOSIT_LOOKUP_FAILED
- DEPOSIT_MISMATCH
- DEPOSIT_STALE
- TXID_REUSED
- CHAIN_UNSUPPORTED
- WINDOW_EXPIRED
- OWNERSHIP_CHANGED
- METHOD_SWITCHED
- REVIEW_REJECTED
- ABANDONED
description: >-
Why a wallet-ownership proof, or its last attempt, fell short of
VERIFIED. Empty when nothing failed. A PENDING proof can carry one: the
last attempt failed and the end user can try again. DEPOSIT_MISMATCH,
DEPOSIT_STALE, TXID_REUSED and REVIEW_REJECTED close the proof as
REJECTED. SIGNATURE_INVALID: the signature does not match the wallet and
challenge. SIGNATURE_UNSUPPORTED_SCHEME: the wallet signed in a format
Didit does not verify. DEPOSIT_NOT_FOUND, DEPOSIT_UNCONFIRMED,
DEPOSIT_LOOKUP_FAILED: the test deposit is not readable or not confirmed
yet; Didit keeps checking it until the test window closes.
DEPOSIT_MISMATCH: the transaction does not send the expected amount from
the wallet to the deposit address. DEPOSIT_STALE: the transaction
predates the challenge. TXID_REUSED: the transaction already proved
another wallet. CHAIN_UNSUPPORTED: the method is not available on this
chain. WINDOW_EXPIRED: the test window closed. OWNERSHIP_CHANGED: the
wallet's holder changed, or the wallet was deleted from your address
book, after the widget session was minted. METHOD_SWITCHED: the end user
picked another method before finishing this one. REVIEW_REJECTED: your
reviewer rejected the screenshot. ABANDONED: the widget session lapsed
before the end user finished.
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.