---
title: "Get Transaction by ID"
method: GET
path: "/financials/transactions/{transaction_id}"
tags: ["Transaction"]
---

# Get Transaction by ID

`GET /financials/transactions/{transaction_id}`

Get a Transaction by ID.

## Path parameters

- `transaction_id` integer, required

## Headers

- `x-api-key` string, required

## Response `200`

Transaction Data

- ResponseTransaction — Output for the get Transaction Query
  - `id` integer — Transaction Id
  - `name` string — Transaction Name
  - `invoice_id` integer — invoice_header_id
  - `payment_method_id` integer — Payment Method Identifier
  - `location_id` integer — Location Identifier
  - `amount` number — Amount
  - `fees` number — Fees
  - `net_amount` number — NetAmount
  - `check_number` string — Check Number
  - `transaction_type_id` integer — Transaction Type Id
  - `transaction_type` string — Transaction Type
  - `transaction_result_id` integer — Transaction Result Id
  - `transaction_result` string — Transaction Result
  - `order_id` string — Order Identifier
  - `error_code` string — Error Code
  - `error_text` string — Error Text
  - `auth_text` string — Auth Text
  - `reference_number` string — Reference Number
  - `parent_transaction_id` integer — Parent Transaction Identifier
  - `has_settled` boolean — Has Settled
  - `status_updated_on` string, date-time — Status Updated On Date Time
  - `credit_card_type` string — Credit Card Type
  - `transaction_datetime` string, date-time — Transaction Date Time
  - `is_pending` boolean — Is Pending
  - `settle_datetime` string, date-time — Settle Date Time
  - `effective_datetime` string, date-time — Effective Date Time
  - `created` Created — Record creation data.
    - `created_by_id` integer — Unique ID of the user that created the record.
    - `created_by` string — Name of the user that created the record.
    - `created_on_datetime` string, date-time — Datetime on which the record was created.
  - `updated` Updated — Update info
    - `updated_by_id` integer — Unique ID of the user that last updated the record.
    - `updated_by` string — Name of the user that most recently updated the record.
    - `updated_on_datetime` string, date-time — Datetime on which the record was last updated.
  - `passed_fees` number — Passed Fees amount
  - `wodify_validation_result` string — The purpose of this attribute is to save any UserException message, that is, and user friendly message that should be shown to the end user. All methods should have, just like service actions: - an UserException with Abort Transaction = Yes, and a Log Error = No - an AllExceptions with Abort Transaction = Yes, and a Log Error = Yes With this, any known issue that we don't consider an error log, like a business validation, we raise it to be catch in the UserException and we don't log it. Then, in the OnResponse of the full REST service, the Build_Response_JSON action will take care on the output json format. An Exception will have the default formatted error message. If its an AllException, it will log the error so that we can fix it. If its a UserException, it will deliver as an error but it won't log it as an error. A success output will not have this attribute, the Build_Response_JSON will remove it from the final output.

---

[API](https://skmtc.net/wodify/apis/leads.md) · [All operations](https://skmtc.net/wodify/apis/leads/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/wodify/leads/versions/974500ca0714/schema)