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

# POST /transactions/{id}

`POST /transactions/{id}`

Modify a pending Award Transaction with Transaction ID

## Request body

- ModifyPendingAwardTransactionWithTransactionIdRequestBody
  - `transaction_attributes` string, json — <p>Every award activity can be modified using this API. You can change the custom attributes for each activity as well as the predefined attributes.</p> <p><strong>Let's take the example of made_a_purchase activity:</strong></p> <p>Mandatory attributes are order_total and order_subtotal.</p> <p>A sample structure of the transaction_attributes for the made_a_purchase activity is given below:</p> <p><code class="c-mrkdwn__code" data-stringify-type="code">{</code><br /><code class="c-mrkdwn__code" data-stringify-type="code">"tags" : ["tag1","tag2"], </code><br /><code class="c-mrkdwn__code" data-stringify-type="code">"reason" : "purchase",</code><br /><code class="c-mrkdwn__code" data-stringify-type="code">"coupons" : "$5OFFVYZ",</code><br /><code class="c-mrkdwn__code" data-stringify-type="code">"order_total" : "1000",</code><br /><code class="c-mrkdwn__code" data-stringify-type="code">"order_subtotal" : "1000",</code></p> <p><code class="c-mrkdwn__code" data-stringify-type="code">"products" : [{</code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> "product_id": "112", </code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> "product_quantity": "1", </code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> "product_category": "tshirt", </code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> "product_price": "15", </code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> "product_title": "Sweatshirt", </code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> "product_image_url": "" </code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> },</code></p> <p><code class="c-mrkdwn__code" data-stringify-type="code">{</code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> "product_id": "980", </code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> "product_quantity": "2", </code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> "product_category": "Sales", </code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> "product_price": "10.017", </code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> "product_title": "Pant", </code><br /><code class="c-mrkdwn__code" data-stringify-type="code"> "product_image_url": ""</code><br /><code class="c-mrkdwn__code" data-stringify-type="code">}]</code></p> <p><code class="c-mrkdwn__code" data-stringify-type="code">}</code></p> <p><strong>Note:</strong> You cannot modify the upload_a_photo, submit_a_receipt and code_submission activities.<code class="c-mrkdwn__code" data-stringify-type="code"></code></p> <p>We are also accepting product quantities in decimal values.</p>
  - `approval_date` string

## Response `200`

200

- ModifyPendingAwardTransactionWithTransactionIdDataObject
  - `data` ModifyPendingAwardTransactionWithTransactionIdResponseObject
    - `status` string — The status of the transaction. It will be "pending" for Modify 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` ModifyPendingAwardTransactionWithTransactionIdAwardInfoObject
      - `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 "pending" for Modify API.
      - `activity_name` string — The activity name stored with Zinrelo.
    - `id` string — The internal ID generated by Zinrelo.
    - `approver_details` ModifyPendingAwardTransactionWithTransactionIdApproverDetailsObject
      - `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 award API, it will always be tagged as "award."
    - `transaction_attributes` ModifyPendingAwardTransactionWithTransactionIdTransactionAttributesRequestBody — By utilizing transaction attributes, you can define attributes for transactions. You can leverage these attributes for personalization and reporting purposes. For more details, refer- https://help.zinrelo.com/docs/custom-attributes
      - `tags` string[]
      - `reason` string
      - `coupons` string
      - `order_total` string
      - `order_subtotal` string
      - `products` object[]
        - `product_id` string
        - `product_quantity` string
        - `product_category` string
        - `product_price` string
        - `product_title` string
        - `product_image_url` string
    - `additional_data` ModifyPendingAwardTransactionWithTransactionIdAdditionalDataObject
      - `activity_multiplier` integer — For activities such as "made_a_purchase," this represents the points spent per dollar.
    - `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)