---
title: "POST /transactions/{id}/reject"
method: POST
path: "/transactions/{id}/reject"
---

# POST /transactions/{id}/reject

`POST /transactions/{id}/reject`

## Response `200`

200

- RejectPendingAwardRedeemTransactionUsingCustomAttributesDataObject
  - `data` RejectPendingAwardRedeemTransactionUsingCustomAttributesResponseObject
    - `status` string — The status of the transaction. It will be "rejected" for reject API.
    - `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` RejectPendingAwardRedeemTransactionUsingCustomAttributesAwardInfoObject
      - `activity_id` string — The unique ID of the activity assigned by Zinrelo.
      - `points` integer — The points awarded for an activity.
      - `points_status` string — This is point status, which will be "rejected" for reject API.
      - `activity_name` string — The activity name stored with Zinrelo.
    - `id` string — The internal ID generated by Zinrelo.
    - `approver_details` RejectPendingAwardRedeemTransactionUsingCustomAttributesApproverDetailsObject
      - `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." Similarly, fr the award API, it will always be tagged as "award."
    - `transaction_attributes` unknown
    - `additional_data` RejectPendingAwardRedeemTransactionUsingCustomAttributesAdditionalDataObject
      - `activity_multiplier` integer — For activities such as "made_a_purchase," this represents the points spent per dollar.
      - `points_to_be_redeemed` integer — Points for redemption.
    - `reward_info` RejectPendingAwardRedeemTransactionUsingCustomAttributesRewardInfoObject
      - `reward_name` string — The name of the reward stored in Zinrelo.
      - `points_status` string — The status of the points- "redemption_cancelled."
      - `coupon_code` string — The coupon code used for redemption.
      - `reward_link` string — The reward link.
      - `reward_id` string — The unique reward ID assigned by Zinrelo.
      - `points` integer — The number of points redeemed by the member.
    - `redemptions_list` unknown[] — The redemption list is empty in scenarios where the transaction is in a pending state or when the points are either exhausted or pending.
      - unknown
  - `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)