Skip to main content
POST
/
v1
/
loyalties
/
members
/
{memberId}
/
pending-points
/
{pendingPointsId}
/
activate
Activate Member Pending Points
curl --request POST \
  --url https://{cluster}.voucherify.io/v1/loyalties/members/{memberId}/pending-points/{pendingPointsId}/activate \
  --header 'Authorization: Bearer <token>' \
  --header 'X-App-Id: <api-key>' \
  --header 'X-App-Token: <api-key>'
{
"points": 1,
"total": 11,
"balance": 10,
"type": "loyalty_card",
"object": "balance",
"related_object": {
"type": "voucher",
"id": "v_abCdEfghI1JKLMNPqRS2Tu3vWXyza4bc"
},
"operation_type": "MANUAL"
}

Authorizations

X-App-Id
string
header
required
X-App-Token
string
header
required
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Path Parameters

memberId
string
required

Unique loyalty card code assigned to a particular customer.

Example:

"MmFAzfDe"

pendingPointsId
string
required

Unique pending point identifier, assigned by Voucherify.

Response

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

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
enum<string>
default:loyalty_card
required

The type of the voucher being modified. For pending points, it is always loyalty_card.

Available options:
loyalty_card
object
enum<string>
default:balance
required

The type of the object represented by JSON. Default is balance.

Available options:
balance

Defines the resource that is being modified.

operation_type
enum<string>
default:MANUAL
required

The type of the operation being performed.

Available options:
MANUAL
I