> ## 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. # Get DICT funds-recovery tracking graph > Fetches the AUTOMATED-flow fraud-tracking graph from BACEN and projects it verbatim. The manual createTrackingGraph POST is BACEN-deprecated; only this read is current. ## OpenAPI ````yaml en/openapi/v3-current/spi-dict.yaml get /api/v1/dict/funds-recoveries/{id}/tracking-graph openapi: 3.1.0 info: contact: email: contact@lerian.studio name: Lerian Studio url: https://lerian.studio description: >- OpenAPI 3.1 surface for the DICT (Diretório de Identificadores de Contas Transacionais) capability of Lerian SPI, the direct integration between the institution and the Brazilian Instant Payment System (SPI/Pix). It covers the PIX key lifecycle, portability and ownership claims, infraction reports, refunds, fraud markers, synchronous DICT reports, and the internal reconciliation and provisioning operations that keep the key directory consistent. license: name: Lerian Studio General License title: Lerian SPI — DICT API version: 1.0.0 servers: - url: https://spi.sandbox.lerian.net security: [] tags: - description: 'PIX key lifecycle: register, list, search, lookup, delete, and statistics.' name: Keys - description: >- PIX key portability and ownership claims through their full lifecycle (initiate, confirm, reject, cancel, acknowledge, complete). name: Claims - description: 'DICT infraction reports: create, list, and retrieve.' name: Infractions - description: 'DICT refund requests: create, list, and retrieve.' name: Refunds - description: 'PIX fraud markers: create, list, and statistics.' name: Fraud Markers - description: >- Synchronous reports over Lerian SPI's own DICT record: COUNT(*) summaries of keys (by type/status) and claims (by type/status + open-past-deadline). COUNT-only — DICT holds no money. name: Reports - description: >- Internal DICT operations: reconciliation runs, participant ISPB provisioning, claim deadline processing, and orphaned-key cleanup. name: Internal paths: /api/v1/dict/funds-recoveries/{id}/tracking-graph: get: tags: - Funds Recoveries summary: Get DICT funds-recovery tracking graph description: >- Fetches the AUTOMATED-flow fraud-tracking graph from BACEN and projects it verbatim. The manual createTrackingGraph POST is BACEN-deprecated; only this read is current. operationId: getFundsRecoveryTrackingGraph parameters: - description: >- Funds recovery UUID (local record id); the graph is fetched from BACEN by its assigned id in: path name: id required: true schema: description: >- Funds recovery UUID (local record id); the graph is fetched from BACEN by its assigned id type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/TrackingGraphResponse' description: >- BACEN-projected fraud-tracking graph, verbatim, with no local computation description: OK default: content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Error security: - BearerAuth: [] components: schemas: TrackingGraphResponse: additionalProperties: false properties: accounts: description: Graph account nodes items: $ref: '#/components/schemas/TrackingGraphAccountResponse' type: - array - 'null' fundsRecoveryId: description: BACEN-assigned funds-recovery id the graph belongs to examples: - ca1b9c01-ff9e-4a58-90ab-d31512e15ce0 type: string persons: description: Graph person nodes (anonymised) items: $ref: '#/components/schemas/TrackingGraphPersonResponse' type: - array - 'null' rootTransactionId: description: Originating fraudulent transaction end-to-end id examples: - E9999901012341234123412345678900 type: string transactions: description: Graph transaction edges items: $ref: '#/components/schemas/TrackingGraphTransactionResponse' type: - array - 'null' required: - fundsRecoveryId - rootTransactionId - persons - accounts - transactions 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 type: object TrackingGraphAccountResponse: additionalProperties: false properties: id: description: Graph-local node id (NOT a real account identifier) examples: - 1 format: int64 type: integer openingDate: description: Account opening date (RFC 3339), when present examples: - '2010-01-10T03:00:00Z' type: string ownerId: description: Graph-local person node id that owns this account examples: - 1 format: int64 type: integer participant: description: Account-holding participant ISPB examples: - '99999010' type: string required: - id - ownerId - participant type: object TrackingGraphPersonResponse: additionalProperties: false properties: entityCreationDate: description: Legal-person entity creation date (RFC 3339), when present examples: - '2010-01-10T03:00:00Z' type: string id: description: Graph-local node id (NOT a real person identifier) examples: - 1 format: int64 type: integer type: description: 'Person type: NATURAL_PERSON or LEGAL_PERSON' examples: - NATURAL_PERSON type: string required: - id - type type: object TrackingGraphTransactionResponse: additionalProperties: false properties: amount: description: Transaction amount (BACEN wire value, projected verbatim) examples: - '1000.20' type: string creditorAccountId: description: Graph-local destination account node id examples: - 2 format: int64 type: integer debtorAccountId: description: Graph-local source account node id examples: - 1 format: int64 type: integer id: description: Transaction end-to-end id (edge identifier) examples: - E9999901012341234123412345678900 type: string refundableAmount: description: Refundable amount (BACEN wire value, projected verbatim) examples: - '900.10' type: string settlementTime: description: Settlement timestamp, when present examples: - '2024-10-01T10:00:00.000Z' type: string required: - id - debtorAccountId - creditorAccountId - amount - refundableAmount 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 securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ````