---
title: "Activate Member Pending Points"
method: POST
path: "/v1/loyalties/members/{memberId}/pending-points/{pendingPointsId}/activate"
tags: ["Loyalties"]
---

# Activate Member Pending Points

`POST /v1/loyalties/members/{memberId}/pending-points/{pendingPointsId}/activate`

Activate manually the pending points and add them to the loyalty card. The pending points are determined by the pending point ID.

Once activated, the pending point entry with that ID is not listed by the endpoints: List member ([with campaign ID](/api-reference/loyalties/list-member-pending-points-with-campaign-id), [without campaign ID](/api-reference/loyalties/list-member-pending-points)), [List campaign pending points](/api-reference/loyalties/list-campaign-pending-points).

This **POST** method does not require a request body.

>👍 Configuring pending points
>
>Pending points are configured as part of an earning rule with [POST Create earning rule](/api-reference/loyalties/create-earning-rule) or [PUT Update earning rule](/api-reference/loyalties/update-earning-rule).

## Response `200`

Returns details about the activated pending points, the current point balance, and loyalty card in general.

- LoyaltiesMembersPendingPointsActivateResponseBody — Response body schema for **POST** `/loyalties/members/{memberId}/pending-points/{pendingPointsId}/activate`.
  - `points` integer, required — The number of pending points added to the loyalty card.
  - `total` integer, required — Total number of points incurred over the lifespan of the loyalty card, minus the expired points.
  - `balance` integer, required — The current number of loyalty points after the pending points have been added.
  - `type` 'loyalty_card', required — The type of the voucher being modified. For pending points, it is always `loyalty_card`.
  - `object` 'balance', required — The type of the object represented by JSON. Default is `balance`.
  - `related_object` object, required — Defines the resource that is being modified.
    - `type` 'voucher', required — The object being modified, i.e. `voucher`.
    - `id` string, required — Identifies the voucher that is being modified. This is the unique identifer that was assigned by Voucherify.
  - `operation_type` 'MANUAL', required — The type of the operation being performed.

## Other responses

- `400` — Returns an error if the pending points have been already activated or canceled.
- `404` — Returns an error if the member or pending point ID could not be found.

---

[API](https://skmtc.net/voucherifyio/apis/voucherify-api-async-actions.md) · [All operations](https://skmtc.net/voucherifyio/apis/voucherify-api-async-actions/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/voucherifyio/voucherify-api-async-actions/revisions/4982266e0494/schema)