> ## 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. # Responder a recogida por email: API de Travel Rule > Con la API de Didit, acepta o rechaza un intercambio de Travel Rule desde un enlace de email de un solo uso e indica el nombre del beneficiario. Prompt para la API de respuesta a la recogida por correo electrónico Copiar el prompt al portapapeles \

\`Accept or decline a pending Travel Rule exchange from a one-time email pickup link - the counterparty-facing side of Didit's EMAIL fallback rail.

Endpoint:
POST https://verification.didit.me/v3/travel-rule/pickup/{token}/respond/

Authentication:
None - the one-time link token is the credential.

Request body (application/json):
\{"decision": "accept", "beneficiary_name": "Carlos Ruiz"}
or
\{"decision": "decline", "decline_reason": "not_our_customer"}

Optional fields:
\- ivms_response - your full IVMS 101 response (up to 16384 characters); its beneficiary name wins over beneficiary_name.
\- beneficiary_name - up to 255 characters.
\- decline_reason - data_mismatch | not_our_customer | wallet_not_hosted | sanctions | risk_appetite | jurisdiction | insufficient_data | other, or empty (the default) for no reason.
\- decline_detail - up to 512 characters; required when decision is decline and decline_reason is other.
\- contact - the contact the link was sent to, as a UUID; when the body leaves it out, the contact query parameter (the link's ?contact= value) is used.

Behavior:
\- accept - the beneficiary name is run through the originator's name rule: the transfer moves to COMPLETED on a match, COUNTERPARTY_MISMATCHED_DATA otherwise. Supply the name exactly as your records hold it. The response is {"status": "..."}.
\- decline - the transfer moves to COUNTERPARTY_VASP_GENERAL_DECLINE, and the sender's timeline records the reason. The response is {"status": "COUNTERPARTY_VASP_GENERAL_DECLINE", "decline_reason": "..."}.
\- You can answer once: afterwards both pickup endpoints return 410.

Failure modes:
\- 404 - unknown token.
\- 410 - the window closed: the counterparty already answered, the transfer left AWAITING_COUNTERPARTY, or the pickup deadline passed.
\- 400 - decision is missing or is not accept or decline, decline_detail is missing for a decline with reason other, ivms_response is not an IVMS 101 object or is too long, or a contact in the body is not a UUID ({"contact": ["Must be a valid UUID."]}).

Counterparty integration guide: /transaction-monitoring/travel-rule-interoperability#email-pickup.`

\
Pegar en ## OpenAPI ````yaml es/openapi-25.json POST /v3/travel-rule/pickup/{token}/respond/ openapi: 3.0.0 info: version: 3.0.0 title: Didit Verification API description: API de verificación de identidad. Autentícate con el encabezado x-api-key. servers: - url: https://verification.didit.me security: [] tags: [] paths: /v3/travel-rule/pickup/{token}/respond/: post: tags: - Travel Rule summary: Responder a una recogida por la vía de correo electrónico description: >- Público, sin autenticación. Acepta o rechaza el intercambio desde el enlace de recogida enviado por correo electrónico. Al aceptar, beneficiary_name se comprueba con la política name_matching_strictness del ordenante. operationId: respondTravelRulePickup parameters: - name: token in: path required: true schema: type: string - name: contact in: query required: false schema: type: string description: >- El valor `?contact=` del enlace. Se usa cuando el cuerpo no envía `contact`. requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/TravelRulePickupRespondRequest' example: decision: accept beneficiary_name: Carlos Ruiz responses: '200': description: >- El estado resultante del intercambio: COMPLETED o COUNTERPARTY_MISMATCHED_DATA tras una aceptación, COUNTERPARTY_VASP_GENERAL_DECLINE tras un rechazo, que además devuelve `decline_reason`. content: application/json: schema: type: object properties: status: type: string decline_reason: type: string description: Presente tras un rechazo. examples: accepted: value: status: COMPLETED declined: value: status: COUNTERPARTY_VASP_GENERAL_DECLINE decline_reason: not_our_customer '400': description: >- Un campo no es válido: por ejemplo, falta `decision` o no es `accept` ni `decline`, falta `decline_detail` en un rechazo con `decline_reason: other`, un `ivms_response` que no es un objeto IVMS 101 o supera los 16384 caracteres, o un `contact` del cuerpo que no es un UUID (`{"contact": ["Must be a valid UUID."]}`). content: application/json: example: decline_detail: - Say what the reason is when you choose another reason. '404': description: Token desconocido. '410': description: >- El plazo se ha cerrado: la contraparte ya respondió, la transferencia salió de AWAITING_COUNTERPARTY o venció la fecha límite. security: - {} x-codeSamples: - lang: curl label: curl source: >- curl -X POST https://verification.didit.me/v3/travel-rule/pickup/{token}/respond/ \ -H 'Content-Type: application/json' \ -d '{"decision": "accept", "beneficiary_name": "Carlos Ruiz"}' components: schemas: TravelRulePickupRespondRequest: type: object required: - decision properties: decision: type: string enum: - accept - decline beneficiary_name: type: string description: >- El nombre del beneficiario tal como figura en tus registros, evaluado con la regla de nombres del VASP emisor. `ivms_response` tiene prioridad cuando indica el nombre del beneficiario. maxLength: 255 decline_reason: type: string enum: - '' - data_mismatch - not_our_customer - wallet_not_hosted - sanctions - risk_appetite - jurisdiction - insufficient_data - other description: >- Por qué rechazas. Se registra en la cronología de la transferencia del VASP emisor. Vacío (el valor predeterminado) cuando no indicas ningún motivo. decline_detail: type: string maxLength: 512 description: >- Texto libre; obligatorio cuando `decision` es `decline` y `decline_reason` es `other`. ivms_response: type: object description: >- Tu respuesta IVMS 101 completa. Su nombre de beneficiario prevalece sobre `beneficiary_name`. contact: type: string format: uuid description: >- El contacto al que se envió el enlace, tomado del valor `?contact=` del enlace. Si el cuerpo no lo incluye, se usa el parámetro de consulta `contact`. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.