---
title: "POST /transactions/deduct"
method: POST
path: "/transactions/deduct"
---

# POST /transactions/deduct

`POST /transactions/deduct`

## Request body

- DeductPointsRequestBody
  - `member_id` string, required — Unique Identifier (Member ID) for the member object in the client’s system which was used while creating a member in Zinrelo.
  - `points_to_be_deducted` integer, required — Number of points to be deducted.
  - `transaction_attributes` string, json — <p>Apart from the above parameters, you can also pass custom attributes for deduct activities, like <strong>reason and tags.&nbsp;</strong></p> <p>For example:</p> <p><code class="c-mrkdwn__code" data-stringify-type="code">{</code><br /><code class="c-mrkdwn__code" data-stringify-type="code">"reason" : "deduct", </code><br /><code class="c-mrkdwn__code" data-stringify-type="code">"tags" : ["deductionmade","productreturned"]</code><br /><code class="c-mrkdwn__code" data-stringify-type="code">} </code></p>

## Response `200`

200

- DeductPointsDataObject
  - `data` DeductPointsResponseObject
    - `status` string — The status could be either approved, rejected, or pending.
    - `transaction_attributes` DeductPointsTransactionAttributesObject — 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
      - `reason` string — The reason behind the transaction.
      - `tags` string[] — The tags assigned for the transaction.
    - `last_modified_date` string — The most recent date on which deduct transaction was updated.
    - `approver_details` DeductPointsApproverDetailsObject
      - `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 deduct transaction was approved.
    - `member_id` string — The unique identifier of the member defined by an Admin.
    - `created_date` string — The date on which deduct transaction was created.
    - `transaction_type` string — This field specifies the transaction type. In the case of the deduct API, it will always be designated as "deduct."
    - `id` string — The internal ID generated by Zinrelo.
    - `deduct_info` DeductPointsDeductInfoObject
      - `points` integer — The number of points that are deducted from the member's account.
      - `points_status` string — The point status could be either "deducted," "rejected" or "pending_deducted." - "deducted": This status indicates that the points have already been deducted from the member's account. - "pending_deducted": This status suggests that the deduction action is in a pending state. - "rejected"- This status indicates that the transaction has been rejected.
  - `success` boolean

## Other responses

- `400` — 400

---

[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/revisions/c12d3d379897/schema)