> ## Documentation Index > Fetch the complete documentation index at: https://docs.getpara.com/llms.txt > Use this file to discover all available pages before exploring further. # Get Transaction > Look up a single persisted REST transaction record by id. Returns `404` with an identical body for records that do not exist or that belong to a different partner. ## OpenAPI ````yaml /openapi.yaml get /v1/wallets/{walletId}/transactions/{transactionId} openapi: 3.0.3 info: title: Para REST API version: '1.0' description: Server-to-server wallet creation and signing over HTTP servers: - url: https://api.beta.getpara.com description: Beta - url: https://api.getpara.com description: Production security: - ApiKeyAuth: [] paths: /v1/wallets/{walletId}/transactions/{transactionId}: get: tags: - Signing summary: Get Transaction description: > Look up a single persisted REST transaction record by id. Returns `404` with an identical body for records that do not exist or that belong to a different partner. operationId: getRestTransaction parameters: - $ref: '#/components/parameters/WalletId' - $ref: '#/components/parameters/RequestId' - name: transactionId in: path required: true description: >- Transaction record id returned by `POST /transfer` or `POST /sign-transaction` with `broadcast: true`. schema: type: string format: uuid responses: '200': description: Transaction record content: application/json: schema: $ref: '#/components/schemas/RestTransaction' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/TooManyRequests' '500': $ref: '#/components/responses/ServerError' components: parameters: WalletId: name: walletId in: path required: true description: Wallet ID schema: type: string example: 0a1b2c3d-4e5f-6789-abcd-ef0123456789 RequestId: name: X-Request-Id in: header required: false description: UUID for request tracing. Para returns one if omitted. schema: type: string format: uuid schemas: RestTransaction: type: object required: - transactionId - walletId - walletType - intentKind - status - createdAt properties: transactionId: type: string format: uuid example: 550e8400-e29b-41d4-a716-446655440000 walletId: type: string format: uuid walletType: type: string enum: - EVM - SOLANA intentKind: type: string enum: - transfer - sign_transaction description: REST operation that created the record. chainId: type: string description: EVM chain ID (EVM records only). network: type: string enum: - SOLANA - SOLANA_DEVNET description: Solana network (Solana records only). to: type: string description: >- Destination address. Absent for Solana `sign_transaction` records because Para does not decode arbitrary Solana instructions. value: type: string description: >- Transfer amount in smallest unit (wei / lamports / token smallest unit), or EVM `sign_transaction` value when supplied. tokenAddress: type: string description: >- Token contract (ERC-20 / SPL mint) address if a token transfer, else absent. Always absent for `sign_transaction` records. status: type: string enum: - pending - submitted - confirmed - reverted - failed description: > Lifecycle state. `pending` = row inserted, not yet broadcast. `submitted` = accepted by the RPC. `confirmed` = included in a block, not reverted. `reverted` = included on-chain but execution failed. `failed` = never broadcast, or broadcast was rejected by the RPC. `submitted`, `confirmed`, `reverted`, and `failed` are terminal from the partner's POV except that `submitted` may still transition via monitoring. **Partners must treat unknown status values as non-terminal** — future versions may add `finalized` or `replaced`. hash: type: string description: Transaction hash (present once submitted). blockNumber: type: string description: >- Block number as a decimal string (present when confirmed or reverted). blockHash: type: string failureStage: type: string enum: - mpc_sign - signature_apply - signer_verify - broadcast - monitor_timeout description: Stage at which the pipeline failed (when `status = failed`). failureCode: type: string description: >- Structured error code from the broadcast helper when the RPC rejected the transaction. failureMessage: type: string description: Truncated error message (max 512 chars). createdAt: type: string format: date-time submittedAt: type: string format: date-time description: Set when status first moves to `submitted`. resolvedAt: type: string format: date-time description: >- Set when status reaches a terminal value (`confirmed`, `reverted`, `failed`). Error: type: object required: - code - message properties: code: type: string description: Machine-readable error code for programmatic handling example: INVALID_REQUEST message: type: string description: Human-readable error message transactionId: type: string format: uuid description: >- Persisted transaction record id. Present only when a broadcast request failed after a history row was created. failureStage: type: string enum: - mpc_sign - signature_apply - signer_verify - broadcast - monitor_timeout description: >- Which stage of the broadcast lifecycle failed. Present on persisted broadcast failures. failureCode: type: string description: >- Machine-readable failure reason from the underlying broadcast helper (e.g. `INSUFFICIENT_NATIVE_BALANCE`, `EXECUTION_FAILED`). Present on broadcast-stage failures. signedTransaction: type: string description: >- Signed transaction bytes. Present on broadcast failures that happen after signing completed. additionalProperties: true description: > All error responses include `code` and `message` fields. Some errors include extra fields (e.g. `walletId` on 409 Conflict). Broadcast failures that occur after a persisted transaction row is created include `transactionId`, `failureStage`, and (on broadcast-stage failures) `failureCode`, and also set the `x-transaction-id` response header. If signing completed before the failure, `signedTransaction` is included so callers can inspect or retry the already-signed bytes. Common error codes: `INVALID_REQUEST`, `UNAUTHORIZED`, `FORBIDDEN`, `NOT_FOUND`, `CONFLICT`, `WALLET_ALREADY_EXISTS`, `WALLET_ALREADY_CLAIMED`, `RATE_LIMITED`, `INTERNAL_ERROR`. responses: BadRequest: description: Invalid request body content: application/json: schema: $ref: '#/components/schemas/Error' example: code: INVALID_REQUEST message: type must be one of EVM, SOLANA, COSMOS, STELLAR Unauthorized: description: API key not provided content: application/json: schema: $ref: '#/components/schemas/Error' example: code: UNAUTHORIZED message: secret api key not provided Forbidden: description: Invalid API key content: application/json: schema: $ref: '#/components/schemas/Error' example: code: FORBIDDEN message: invalid secret api key NotFound: description: Wallet not found content: application/json: schema: $ref: '#/components/schemas/Error' example: code: NOT_FOUND message: wallet not found TooManyRequests: description: Rate limit exceeded headers: Retry-After: schema: type: integer description: Seconds until the rate limit window resets example: 60 content: application/json: schema: $ref: '#/components/schemas/Error' example: code: RATE_LIMITED message: Rate limit exceeded, try again shortly. ServerError: description: Internal server error content: application/json: schema: $ref: '#/components/schemas/Error' example: code: INTERNAL_ERROR message: Internal Server Error securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-Key description: Your partner secret key (server-side only) x-default: sk_your_secret_key_here ````