> ## 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. # Acknowledge a Pix key claim > Acknowledges an OPEN donor-side Pix key claim when the automatic acknowledgement needs to be retried. The caller must be the donor participant. The operation has no request body. ## OpenAPI ````yaml en/openapi/v3-current/pix-lerian-dict.yaml POST /claims/{claim_id}/acknowledge 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. license: name: Elastic License 2.0 url: https://www.elastic.co/licensing/elastic-license title: Pix Lerian — DICT version: release-candidate 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: Register, retrieve, list, update, and remove Pix keys. name: Entries - description: Look up Pix keys and check whether keys exist in the DICT directory. name: Keys - description: Manage ownership and portability claims for Pix keys. name: Claims - 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: Create, query, cancel, and settle MED 2.0 refunds. name: Refunds - description: Create, query, list, and cancel DICT fraud markers. name: Fraud Markers paths: /claims/{claim_id}/acknowledge: post: tags: - Claims summary: Acknowledge a Pix key claim description: >- Acknowledges an OPEN donor-side Pix key claim when the automatic acknowledgement needs to be retried. The caller must be the donor participant. The operation has no request body. operationId: acknowledgeClaim parameters: - description: Client-generated key used to retry exactly the same request safely. in: header name: Idempotency-Key required: true schema: maxLength: 64 minLength: 1 type: string description: >- Client-generated key used to retry exactly the same request safely. example: pix-demo-20260903-000001 - in: path name: claim_id required: true schema: examples: - 019606c3-5d6e-7f80-1b23-456789012cde type: string example: 019606c3-5d6e-7f80-1b23-456789012cde responses: '202': content: application/json: schema: $ref: '#/components/schemas/AcknowledgeClaimResponse' examples: fictitiousExample: summary: Fictitious example value: claimId: 019606c3-5d6e-7f80-1b23-456789012cde status: WAITING_RESOLUTION description: Accepted '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' description: >- Idempotency-Key absent or longer than 64 bytes (PIX-0030). Legacy {code,title,message} envelope, NOT problem+json. '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: >- Idempotency-Key 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. default: content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Error x-codeSamples: - lang: bash label: cURL with fictitious data source: |- curl --request POST \ --url https://api.example.com/dict-hub/v1/claims/019606c3-5d6e-7f80-1b23-456789012cde/acknowledge \ --header 'Authorization: Bearer demo-access-token' \ --header 'Idempotency-Key: pix-demo-20260903-000001' components: schemas: AcknowledgeClaimResponse: additionalProperties: false properties: claimId: examples: - 019606c3-5d6e-7f80-1b23-456789012cde type: string status: examples: - WAITING_RESOLUTION type: string required: - claimId - status 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 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 ````