Skip to main content
POST
/
api
/
v4.0
/
integrations
/
transactions
/
manual
cURL
curl --request POST \
  --url https://api.gameball.co/api/v4.0/integrations/transactions/manual \
  --header 'Content-Type: application/json' \
  --header 'apikey: <api-key>' \
  --data '
{
  "customerId": "cust_abc12345xyz67890",
  "transactionId": "txn543211",
  "transactionTime": "2024-10-11T15:54:10.944Z",
  "username": "admin_user",
  "reason": "Referral bonus",
  "points": 50,
  "email": "john.doe@example.com",
  "mobile": "+1234567890",
  "amount": 0
}
'
{
  "customerId": "cust_abc12345xyz67890",
  "gameballTransactionId": 11035201,
  "transactionId": "txn54321221",
  "points": 50,
  "amount": 5
}

​
Add Manual Transaction

This API allows for the manual addition or deduction of points for a customer in Gameball. It provides flexibility in managing loyalty points, enabling adjustments based on specific needs or circumstances.
Channel Merging Available If your system uses different customer IDs across multiple channels (e.g., online and offline), Gameball’s channel merging feature helps unify customer profiles. By including the customer’s mobile number or email (based on your merging configuration) with each request, Gameball will combine activities into a single profile.
Security: Provide both apikey and secretkey headers.

Authorizations

​
apikey
string
header
required

Body

application/json
​
customerId
string
required

Unique identifier for the customer that you can reference across the customer's whole lifetime. Could be a database ID, random string, email, or anything that uniquely identifies the customer.

Example:

"cust_abc12345xyz67890"

​
transactionId
string
required

A unique identifier for a transaction in your system (e.g., order number or invoice number). This ID can be used to reverse, cancel, or refund any reward or redemption transactions in Gameball.

Example:

"txn543211"

​
transactionTime
string<date-time>
required

The time of the transaction in your system (e.g., order datetime, invoice datetime).

Example:

"2024-10-11T15:54:10.944Z"

​
username
string
required

The username of the admin performing the manual transaction.

Example:

"admin_user"

​
reason
string
required

Reason for manually rewarding or deducting points (e.g., 'Referral bonus').

Example:

"Referral bonus"

​
points
integer
required

The number of points to be rewarded or deducted (should be positive for rewards and negative for deductions).

Example:

50

​
email
string

Customer's email address. This is required if your account uses email-based channel merging.

Example:

"john.doe@example.com"

​
mobile
string

Customer's mobile number. This is required if your account uses mobile-based channel merging.

Example:

"+1234567890"

​
amount
number

The monetary value (in system currency) associated with the transaction.

Example:

0

Response

200 - application/json

Manual transaction added successfully

​
customerId
string

Unique identifier for the customer that you can reference across the customer's whole lifetime. Could be a database ID, random string, email, or anything that uniquely identifies the customer.

Example:

"cust_abc12345xyz67890"

​
gameballTransactionId
number

The unique identifier for the transaction within Gameball.

Example:

11035201

​
transactionId
string

A unique identifier for a transaction in your system (e.g., order number or invoice number). This ID can be used to reverse, cancel, or refund any reward or redemption transactions in Gameball.

Example:

"txn54321221"

​
points
number

The number of points rewarded or deducted in the transaction.

Example:

50

​
amount
number

The monetary value processed in the transaction.

Example:

5