Allows manual adjustments to a customer's loyalty points balance.
🔑Scopes
loyalty_program.read_write - Loyalty Program Read & Write
Request
Header Params
Accept
string
required
Specifies the Media Types acceptable for the client. In this case, it signals that the client expects a response in the JSON format.
Default:
application/json
Authorization
string
required
The Authorization token is a unique key given to the third-party application (Partner) by Zid. It is used to authenticate the API requests made by the Partner application. The token verifies the partner's identity and ensures they have permission to access Zid's API but does not provide any specific user or store information. It should be included in the header of API requests when the partner application needs to access Zid's API.
The User-Agent header contains information about the user agent (browser or app) making the request. It allows the server to provide a tailored response depending on the user agent's capabilities and preferences.
Example:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.82 Safari/537.36
Accept-Language
enum<string>
optional
Preferred language for the response. Defaults to en if not specified.
Allowed values:
enar
Example:
en
X-Manager-Token
string
required
This token is used to authenticate and access information related to the store. It is obtained through an OAuth mechanism and is required to perform operations on the store's data. The X-Manager-Token should be included in the header of API requests that require store-related information.
The customer points balance is adjusted successfully.
Body
status
string
optional
Indicates the overall status of the API response.
data
object
optional
The data object contains information about the points adjustment made to the customer's account.
date
string
optional
The timestamp indicating when the points adjustment was made. The date and time are provided in ISO 8601 format.
Example:
2024-08-19T07:01:03.580901Z
reason
string
optional
The reason for adjusting the points.
Example:
test
points
integer
optional
The number of points that were adjusted (added or subtracted) in the customer's account.
Example:
100
direction
string
optional
Indicates whether points were added or subtracted from the customer's account. A value of "+" means points were added, while a value of "-" would indicate points were subtracted.
Example:
+
type
string
optional
The type of transaction, indicating how the points were adjusted. "ManualAccumulation" suggests that the points were added manually by an administrator or system user.
Example:
ManualAccumulation
order_number
null
optional
The order number associated with this points adjustment.
expiry_date
null
optional
The date and time when the points will expire.
point_status
string
optional
The current status of the points after the adjustment.
Example:
Active
collection_method
string
optional
Describes how the points were added to the customer's account, indicating that this was done manually rather than through an automated process or system trigger.
Example:
Manually added points
message
object
optional
Contains detailed information about the message.
type
string
optional
Specifies the type of message.
code
string
optional
A specific code representing the type.
Example:
MSG_POPUP_OK
name
string
optional
A short, human-readable title or name for the message.
Example:
Adjust customer points
description
string
optional
A detailed description of the message, providing more context.