# To deduct or award loyalty points to multiple members

This method allows you to simultaneously deduct or award points to multiple members. To make a bulk point adjustment you will number each object in the request. Nested within each object, you must include the id, actionId, and activity parameters. If you are manually crediting points or debiting points, you must also include the credit or debit parameter accordingly. If you are crediting points for a point awarding action configured in the loyalty program, you do not need to include the credit parameter, as it will award the member points as configured in the system for that action ID.

Endpoint: POST /bulkpoints
Version: 3.0.0
Security: 

## Request fields (application/json):

  - `1` (object, required)
    Enter the following details of the member.

  - `1.id` (string)
    Enter the member's unique ID.
    Example: "user@domain.com"

  - `1.actionId` (string)
    Enter the unique action ID for awarding or deducting points from the member's account. For instance, the action ID for manual credit is 100.
    Example: "100"

  - `1.activity` (string)
    Enter the activity as CREDIT or DEBIT.
    Example: "CREDIT"

  - `1.debit/credit` (integer)
    Enter the number of points to be credited or debited from the member’s account.
    Example: 100

  - `1.reason` (string)
    Enter the reason for awarding or deducting points from the member's account.
    Example: "Bonus points"

  - `1.storeId` (string)
    Enter the store ID, a unique number used to identify the specific store. Note - If a store ID is provided with any action and it exists in the metadata, all associated attributes of that store will be displayed. If the store ID does not exist in the metadata, it will simply display the store ID itself.
    Example: "IN12369"

## Response 200 fields (application/json):

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

  - `id` (string)
    Displays the unique ID of the member.
    Example: "user@domain.com"

  - `actionId` (string)
    Displays the unique action ID for which the member is awarded or deducted points.
    Example: 101

  - `activity` (string)
    Displays whether the activity is a credit or a debit.
    Example: "CREDIT"

  - `credit/debit` (integer)
    Displays the number of points credited to or debited from the member's account.
    Example: 100

  - `storeDetails` (object)
    Displays the following store details associated with the store. Note - If a store ID is provided with any action and it exists in the metadata, all associated attributes of that store will be displayed. If the store ID does not exist in the metadata, it will simply display the store ID itself.

  - `storeDetails.storeId` (string)
    Displays an identifier for the specific store. It is a unique code assigned to each store.
    Example: "IN12369"

  - `storeDetails.storeName` (string)
    Displays the name associated with the specific store.
    Example: "SHELL"

  - `storeDetails.storeExtendedAttribute` (string)
    Displays all the store extended attributes.
    Example: "Store Location"

  - `pointsAwarded` (integer)
    Displays the number of points awarded to the member’s account for performing the action.
    Example: 100

  - `reason` (string)
    Displays the reason for awarding points to the member’s account.
    Example: "bonus"

  - `updatedAvailablePoints` (integer)
    Displays the updated number of available points in the member’s account after points have been awarded or debited.
    Example: 100

  - `updatedLifetimePoints` (integer)
    Displays the updated total number of points the member has earned in their lifetime with the loyalty program after points have been awarded.
    Example: 200

  - `previousTier` (string)
    Displays the member’s previous tier before the points were awarded or debited.
    Example: "Silver"

  - `updatedUserTier` (string)
    Displays the member’s updated tier after the points are awarded or debited.
    Example: "Gold"


## Response 400 fields

## Response 403 fields

## Response 404 fields

## Response 405 fields

## Response 422 fields