---
title: "GET /tax/transactions/{transaction_id}"
method: GET
path: "/tax/transactions/{transaction_id}"
---

# GET /tax/transactions/{transaction_id}

`GET /tax/transactions/{transaction_id}`

Retrieve the details of a specific transaction

## Path parameters

- `transaction_id` string, required

## Response `200`

Transaction details

- TransactionResponse
  - `id` string — The ID of the `transaction`. We highly recommend you store this value. If you need to refund or query the data from this transaction, you will use this ID as a reference.
  - `object` string — The type of object: `tax.transaction`.
  - `calculation_id` string — The ID of the `calculation` that was used to create this transaction
  - `reference_order_id` string — The unique order ID you provided when creating the `transaction`
  - `transaction_processed_at` number — Unix timestamp in **seconds** representing the date and time your sale was made. If not provided, the date and time this `transaction` was created
  - `customer_currency_code` string — The ISO-4217 currency code of the transaction
  - `filing_currency_code` string — The currency code of the filing that will be used to remit taxes collected on this transaction
  - `line_items` TransactionLineItem[]
    - `product` object
      - `reference_product_name` string
      - `reference_line_item_id` string
      - `reference_product_id` string
      - `product_tax_code` string
    - `tax_jurisdictions` object[]
      - `tax_rate` number — The tax rate percentage applied to this transaction.
      - `tax_due_decimal` number — Tax amount due for this jurisdiction in the currency's smallest unit.
      - `rate_type` string — Descriptive rate classification for this jurisdiction.
      - `fee_amount` number — The flat fee that is added to this transaction. Like all numeric values, this will be returned in cents and should be added directly to the tax amount independent of other percentages. For example, a $100 transaction taxed at 5% and with a `fee_amount: 50` will lead to `($100 * 5% + 0.50) = $5.50` in tax being charged
      - `tax_authority_name` string — Name of the tax authority.
      - `tax_authority_type` string — Type of tax authority (e.g., STATE, COUNTY, CITY, DISTRICT).
      - `tax_type` string — Type of tax: SALES, USE, VAT, or GST.
    - `quantity` number
    - `tax_amount` number
    - `amount_excluding_tax` number
    - `amount_including_tax` number
  - `testmode` boolean — `True` if using a production API key. If `true`, Numeral will record this `transaction` towards your nexus totals. If you're registered and collecting in the relevant jurisdiction, we'll file the tax.
  - `metadata` Metadata — You can store arbitrary keys and values in the metadata. At most 50 keys; each key at most 255 characters; each value must be a string of at most 255 characters (non-string values are rejected).
    - `example_key` string — Storing things like an order number may be useful for reporting and reconciliation.

## Other responses

- `400` — Unexpected error

---

[API](https://skmtc.net/numeral-com/apis/numeral-api.md) · [All operations](https://skmtc.net/numeral-com/apis/numeral-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/numeral-com/numeral-api/revisions/f0af51c3f9b9/schema)
