---
title: "GET /transactions/{id}"
method: GET
path: "/transactions/{id}"
---

# GET /transactions/{id}

`GET /transactions/{id}`

Retrieve a Transaction with Transaction ID

## Response `200`

200

- RetrieveTransactionUsingUniqueTransactionAttributeDataObject
  - `data` RetrieveTransactionUsingUniqueTransactionAttributeResponseObject
    - `status` string — The transaction status. It could be either approved, pending or rejected.
    - `points_expiration_date` string — The date on which points will expire.
    - `auto_approval_date` string — The "auto approval date" for a transaction signifies the date when the transaction will be automatically approved. This approval mechanism can be established through an API or can be configured by setting the "after a fixed duration" option within the approval type in the activities settings page within the admin console. When this specified date arrives, the transaction will undergo automatic approval as per the settings configured.
    - `last_modified_date` string — The recent date on which the transaction was updated.
    - `award_info` RetrieveTransactionUsingUniqueTransactionAwardInfoObject
      - `activity_id` string — The unique ID of the activity assigned by Zinrelo.
      - `points` integer — The points awarded for an activity.
      - `points_status` string — This indicates the status of the points.
      - `activity_name` string — The activity name stored with Zinrelo.
    - `id` string — The internal ID generated by Zinrelo.
    - `approver_details` RetrieveTransactionUsingUniqueTransactionApproverDetailsObjec
      - `approver_name` string — The person or source who approves the transaction.
      - `approver_id` string — The unique ID associated with the approver.
    - `approved_date` string — The date on which the transaction was approved.
    - `member_id` string — The unique identifier of the member defined by an Admin.
    - `created_date` string — The date on which the transaction was created.
    - `transaction_type` string — This field specifies the transaction type. For the redeem API, it will always be labeled as "redeem." For the award API, it will always be tagged as "award." Similarly, for the deduct API, it will always be denoted as "deduct."
    - `transaction_attributes` unknown
    - `additional_data` RetrieveTransactionUsingUniqueTransactionAdditionalDataObject
      - `activity_multiplier` integer — For activities such as "made_a_purchase," this represents the points spent per dollar.
      - `history` unknown[] — This displays the transaction's history before modifications were made.
        - unknown
      - `current_loyalty_level_id` string — Current tier.
      - `custom_attributes` object — By utilizing custom attributes, you can define attributes for both members and transactions. You can leverage these attributes for personalization and reporting purposes. For more details, refer- https://help.zinrelo.com/docs/custom-attributes
      - `points` integer — The points awarded for an activity.
      - `created_time` string — The date on which the transaction was created.
    - `redemptions_list` RetrieveTransactionUsingUniqueTransactionAttributeRedemptionsList[] — The redemption list is empty in scenarios where the transaction is in a pending state or when the points are either exhausted or pending.
      - `redemption_id` string — The unique ID associated with the redemption.
      - `redeemed_points` integer — The number of points redeemed.
      - `id` string — The redemption ID configured in admin console.
  - `success` boolean

## Other responses

- `400` — 400
- `404` — 404

---

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