Subscription Management
The subscription* management endpoints allow you to:
- see all available (webhook) subscriptions and related information
- see detailed information about your (webhook) subscriptions
- delete your subscriptions.
š* By subscriptions, we refer to webhook update subscriptions made in member_changes endpoints.
You will only be able to see the subscriptions connected to your token.
See the endpoints and their functions below:
Endpoint | Function |
---|---|
/v1/subscriptions | See all your subscriptions, their status, creation, and expiration dates |
/v1/subscriptions/{subsription_id} | See the details of your active subscriptions |
DELETE /v1/subscriptions/{subscription_id} | Delete your subscriptions |
Use the endpoint /v1/subscriptions to see all your available subscriptions, their statuses, creation and expiration dates:
- Indicate if you want to see the details of active or expired subscriptions (expired = false OR expired = true) You will automatically see only active subscriptions if you omit the expired = true/false parameter.
- Indicate which page number you wish to see. Each page contains about 1000 subscriptions, so if you have more than 1000 subscriptions, you might need to indicate the page number.
- Replate {JWT} with your API token in the template below:
4. Send the request.
5. Refer to the Body for information about your subscription status:
Data point | Description | Data type |
---|---|---|
id | Subscription identification key. Subscription ID is displayed in the response body after submitting a webhook subscription via member_changes endpoints | String |
status | Subscription status (active or expired) | String |
created_at | Subscription start date in YYYY-MM-DD format | String (date) |
expiring_at | Subscription expiry date in YYYY-MM-DD format | String (date) |
Use the endpoint /v1/subscriptions/{id} to see the details of your expired or active subscriptions:
- Provide your subscription_ID*. š*Subscription ID is displayed in the response body after successfully submitting a webhook subscription via member_changes endpoints.
- Replate {JWT} with your API token.
3. Send the request.
4. You will see the following information in the Response body:
Data point | Description | Data type |
---|---|---|
id | Subscription identification key. | String |
status | Subscription status (active or expired) | String |
created_at | Subscription start date in YYYY-MM-DD format | String (date) |
expiring_at | Subscription expiry date in YYYY-MM-DD format | String (date) |
entity | Subscription entity | String |
es_dsl_query | ES DSL query used to subscribe to changes in a list of profiles | String |
filters | Search filters used to subscribe to changes in a list of profiles | String |
last_webhook_sent | Time of last message sent to your webhook URL in YYYY-MM-DD format | String (date) |
Use the endpoint DELETE /v1/subscriptions/{id} to make your subscriptions inactive.
Use your subscription ID as input to request updates of member profiles or experience changes.
Refer to the template below:
ļ»æ