Skip to main content
PUT
/
v2
/
activities
/
{name}
/
{merchant_id}
cURL
curl --request PUT \
  --url https://api.loyaltylion.com/v2/activities/{name}/{merchant_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{}'
"<string>"

Documentation Index

Fetch the complete documentation index at: https://developers.loyaltylion.com/llms.txt

Use this file to discover all available pages before exploring further.

Use this endpoint to inform us about a change to an activity. For example, if you track a review activity which defaults to pending and your moderator then approves the review, you can send LoyaltyLion an update informing us it has been approved. To update an activity you’ll need the activity name (for example, review) and the merchant_id you sent to LoyaltyLion when you first tracked the activity.

​
Difference between void and decline

Pending activities can be declined, while approved activities can be voided. If you aren’t sure if an activity is pending or approved, you should update the state to declined. This will be treated as void if the activity is approved.

Authorizations

​
Authorization
string
header
required

An API key linked to a Program in LoyaltyLion, with a set of permissions (scopes). API keys can be created manually, or acquired through an OAuth2 flow. The API key should be provided as a Bearer token in the Authorization header

Path Parameters

​
name
string
required

A built-in or custom activity rule name. If you’re tracking a custom rule, this should be the rule identifier; if you’re tracking a built-in activity, the name must be prefixed with a $, for example, $signup

Minimum string length: 1
​
merchant_id
string
required

The unique ID provided when you initially tracked this activity

Minimum string length: 1

Body

application/json

Body

​
state
enum<string>
required

The new state of this activity

Available options:
approved,
declined,
void

Response

204

The response is of type string.

Allowed value: ""