> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Update a funds recovery > Applies a JSON merge-patch (Content-Type: application/merge-patch+json) to the mutable fields (contact information and report details) of a funds recovery owned by the authenticated participant. Only the fields present in the body are changed; any other field (metadata, status, participantId, ...) is rejected with 422. Returns 404 when no active recovery with that ID belongs to the participant and 409 when the recovery's current status no longer allows information changes. ## OpenAPI ````yaml /es/openapi/v3-current/pix-lerian-dict.yaml patch /dict/funds-recoveries/{id} openapi: 3.1.0 info: contact: name: Lerian Studio url: https://lerian.studio description: >- Public API for Pix keys, claims, fraud markers, infraction reports, and MED funds recovery. This release provides a mock-provider integration for testing; live BACEN connectivity is not included. license: name: Lerian Studio General License title: Pix Lerian — DICT version: 1.0.0 servers: - url: https://api.example.com/dict-hub/v1 description: >- Replace the example host with the URL provided during environment onboarding. security: - BearerAuth: [] tags: - description: Manage ownership and portability claims for Pix keys. name: Claims - description: Register, retrieve, list, update, and remove Pix keys. name: Entries - description: Create, query, list, and cancel DICT fraud markers. name: Fraud Markers - description: Manage participant-scoped MED 2.0 funds recoveries. name: Funds Recoveries - description: Manage MED 2.0 infraction reports for the authenticated organization. name: Infraction Reports - description: Look up Pix keys and check whether keys exist in the DICT directory. name: Keys - description: Create, query, cancel, and settle MED 2.0 refunds. name: Refunds paths: /dict/funds-recoveries/{id}: patch: tags: - Funds Recoveries summary: Update a funds recovery description: >- Applies a JSON merge-patch (Content-Type: application/merge-patch+json) to the mutable fields (contact information and report details) of a funds recovery owned by the authenticated participant. Only the fields present in the body are changed; any other field (metadata, status, participantId, ...) is rejected with 422. Returns 404 when no active recovery with that ID belongs to the participant and 409 when the recovery's current status no longer allows information changes. operationId: patchFundsRecovery parameters: - description: >- REQUIRED. Client-supplied replay key, at most 64 bytes. A request without it is refused with PIX-0030 @ 400 before the handler runs. Replaying the same key with a divergent method, URL or body is PIX-0031 @ 412. in: header name: X-Idempotency required: true schema: maxLength: 64 minLength: 1 type: string - description: Funds recovery internal ID (UUID format) in: path name: id required: true schema: description: Funds recovery internal ID (UUID format) examples: - 018f8c1d-1234-7abc-9def-000000000001 type: string - description: Must be application/merge-patch+json. in: header name: Content-Type schema: description: Must be application/merge-patch+json. examples: - application/merge-patch+json type: string requestBody: content: application/merge-patch+json: schema: contentMediaType: application/octet-stream format: binary type: string required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/FundsRecoveryOutput' description: OK '400': content: application/json: example: code: PIX-0030 title: Idempotency Key Required message: >- The Idempotency-Key header is required for this operation and must be within the accepted length. schema: $ref: '#/components/schemas/LegacyErrorEnvelope' application/problem+json: example: type: https://errors.lerian.studio/v1/PIX-0001 title: Bad Request status: 400 detail: Your request is missing one or more required header params. code: PIX-0001 schema: $ref: '#/components/schemas/Detail' description: >- Bad Request (PIX-0001, PIX-0002, PIX-0003, PIX-0017, PIX-0015, PIX-0020, PIX-0107). X-Idempotency absent or longer than 64 bytes (PIX-0030). Legacy {code,title,message} envelope, NOT problem+json. '404': content: application/problem+json: example: type: https://errors.lerian.studio/v1/PIX-0110 title: Not Found status: 404 detail: >- No funds recovery exists with the provided ID for this participant. code: PIX-0110 schema: $ref: '#/components/schemas/Detail' description: Not Found (PIX-0110). '409': content: application/problem+json: example: type: https://errors.lerian.studio/v1/PIX-0113 title: Conflict status: 409 detail: A funds recovery already exists for this root transaction. code: PIX-0113 schema: $ref: '#/components/schemas/Detail' description: Conflict (PIX-0113, PIX-0114, PIX-0118). '412': content: application/json: example: code: PIX-0031 title: Idempotency Key Conflict message: The Idempotency-Key was already used with a different request. schema: $ref: '#/components/schemas/LegacyErrorEnvelope' description: >- X-Idempotency replayed with a divergent request -- a different method, URL (including the path parameter), body, or identity header among X-Account-Id / X-Reason / X-End-To-End-Id (PIX-0031). Legacy {code,title,message} envelope, NOT problem+json. '422': content: application/problem+json: example: type: https://errors.lerian.studio/v1/PIX-0100 title: Unprocessable Entity status: 422 detail: Missing or malformed required fields. code: PIX-0100 schema: $ref: '#/components/schemas/Detail' description: Unprocessable Entity (PIX-0100, PIX-0117). '500': content: application/problem+json: example: type: https://errors.lerian.studio/v1/PIX-0000 title: Internal Server Error status: 500 detail: internal error code: PIX-0000 schema: $ref: '#/components/schemas/Detail' description: Internal Server Error (PIX-0000). '502': content: application/problem+json: example: type: https://errors.lerian.studio/v1/PIX-0141 title: Bad Gateway status: 502 detail: internal error code: PIX-0141 schema: $ref: '#/components/schemas/Detail' description: Bad Gateway (PIX-0141). default: content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Error components: schemas: FundsRecoveryOutput: additionalProperties: false properties: accountId: examples: - 550e8400-e29b-41d4-a716-446655440000 type: string bacenFundsRecoveryId: examples: - 9f3a8b7e-2c1d-4e5a-8b6f-1a2b3c4d5e6f type: string contactInformation: $ref: '#/components/schemas/ContactInformationOutput' correlationId: examples: - 7c9e6679742540de944be07fc1f90ae7 type: string createdAt: examples: - '2026-05-17T13:30:00Z' format: date-time type: string id: examples: - 018f8c1d-1234-7abc-9def-000000000001 type: string metadata: {} participantId: examples: - '12345678' type: string reportDetails: examples: - Victim of a WhatsApp scam type: string reporterParticipant: examples: - '12345678' type: string rootTransactionId: examples: - E12345678202605171530aB3xK9mWq2z type: string situationType: enum: - SCAM - ACCOUNT_TAKEOVER - COERCION - FRAUDULENT_ACCESS - OTHER - UNKNOWN examples: - SCAM type: string status: enum: - CREATED - TRACKED - AWAITING_ANALYSIS - ANALYSED - REFUNDING - COMPLETED - CANCELLED examples: - CREATED type: string trackingGraph: {} trackingGraphParameters: {} updatedAt: examples: - '2026-05-17T13:30:00Z' format: date-time type: string required: - id - bacenFundsRecoveryId - participantId - accountId - rootTransactionId - situationType - status - reporterParticipant - contactInformation - createdAt - updatedAt type: object LegacyErrorEnvelope: additionalProperties: false properties: code: description: PIX-XXXX error code type: string message: description: Human-readable error message type: string title: description: Short error title type: string required: - code - title - message type: object Detail: additionalProperties: false properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). examples: - ERR-0001 type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string upstream: $ref: '#/components/schemas/Upstream' description: >- RFC 9457 extension member: the error a proxied third-party provider reported. Absent unless the emitting service explicitly surfaced one. type: object ContactInformationOutput: additionalProperties: false properties: email: examples: - user@example.com type: string phone: examples: - '+5511999999999' type: string required: - email - phone type: object ErrorDetail: additionalProperties: false properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object Upstream: additionalProperties: false properties: code: description: The upstream provider's own error code, verbatim. examples: - E4001 type: string message: description: >- The upstream provider's own error message, verbatim (bounded, never its raw response body). examples: - account not found at provider type: string type: object securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ````