# Get transaction erasure details

By passing the User ID, use this method to retrieve all transaction erasure details for a loyalty member.
Note: For all date-time fields in the request and response, if the timestamp contains a timezone offset after the + symbol (for example, 2024-07-21T12:30:45+05:30), the value after + will be ignored during processing. Only the date and time portion before the + sign will be considered.

Endpoint: GET /transactionErasure/{{memberId}}
Version: 3.0.0
Security: MuseumPlaceholderAuth

## Security:

  - `MuseumPlaceholderAuth` (unknown)

## Path parameters:

  - `memberId` (string, required)
    Enter the unique ID of the loyalty member.

## Response 200:

  - `200` (unknown)
    successful operation

## Response 200 fields (application/json):

  - `transactiondetails` (object)
    Displays the following parameters-

  - `transactiondetails.userId` (string)
    Displays the unique ID of the loyalty member.
    Example: user@domain.com

  - `transactiondetails.siteId` (string)
    Displays the Annex Cloud site ID for the loyalty program.
    Example: 29235480

  - `transactiondetails.data` (object)
    Displays the following details-

  - `transactiondetails.data.orderId` (string)
    Displays the unique order ID for the order placed by the loyalty member.
    Example: A2034354570

  - `transactiondetails.data.orderDate` (string)
    Displays the date the order was placed in yyyy-MM-dd'T'HH:mm:ssZ format.
    Example: 2022-03-01 00:00:00

  - `transactiondetails.data.eligibleForErasure` (string)
    Displays if the transaction is eligible for erasure or not.
    Example: Yes

  - `transactiondetails.data.pointsRequired` (integer)
    Displays the number of points required for a transaction to erase an eligible transaction.
    Example: 300

  - `transactiondetails.data.previouslyErased` (integer)
    Displays whether the transaction was previously erased or not. In this particular instance, 0 implies previously not erased and 1 means previously erased.
    Example: 0

  - `transactiondetails.data.pointsRefunded` (integer)
    Displays the points refunded to the loyalty member following the reversal of transaction erasure or the cancellation of an order. (In this scenario, the 100 points in the example indicate that the points were utilized to complete transaction erasure. The points are being reimbursed to the member when the transaction erasure is reversed).
    Example: 100

  - `transactiondetails.data.reversal` (string)
    Displays the status of the transaction erasure. In this case, 0 indicates that the transaction has not been reversed, while 1 indicates that it has been reversed.
    Example: 0

  - `transactiondetails.orderAttribute` (object)
    Displays the following details-

  - `transactiondetails.orderAttribute.attribute_1` (string)
    Displays a description of the attributes associated with an order. The order attributes are completely configurable based on the needs of the client.
    Example: Value1

  - `transactiondetails.orderAttribute.pages` (integer)
    Displays the total number of pages that include information on orders placed by a member.
    Example: 4

  - `transactiondetails.orderAttribute.currentPage` (integer)
    Displays the current page number that contains the information related to transaction being erased.
    Example: 1

  - `transactiondetails.orderAttribute.totalOrderCount` (integer)
    Displays the total number of orders placed by the loyalty member.
    Example: 18

## Response 400:

  - `400` (unknown)
    AC1004 Missing Parameters

## Response 403:

  - `403` (unknown)
    AC1009 Member has opted-out

## Response 404:

  - `404` (unknown)
    AC1005 No data found

## Response 500:

  - `500` (unknown)
    Internal Server Error