REST API v3: PUT collection unsubscribe

For every collection you may also set the unsubscribe settings separately. When Copernica’s servers receive an unsubscription the unsubscribe behavior determines what happens with the profile: should it be edited or removed?

To set this algorithm using an API call, make an HTTP PUT request to the following URL:$id/unsubscribe?access_token=xxxx

In this, the variable $id has to be replaced by the numerical identifier of the collection you wish to set the unsubscribe behaviour for. The new setting should be added to the body of the HTTP request.

Available data

The following variables must be put into the body of the request:

  • behavior: the setting itself
  • fields: the new profile setting (only applicable if ‘behavior’ is set to ‘update’)

‘behavior’ has three possible values: 'nothing', 'remove' and 'update'. 'Nothing' means unsubscriptions are simply ignored, 'remove' deletes unsubscribers and 'update' can be used to change a property of the profile such that you can keep the information while respecting their wish not to receive more email.

JSON example

The following JSON demonstrates how to use the API method:

  "behavior": "update",
  "fields": {
    "newsletter": "no"

PHP example

The following PHP script demonstrates how to use the method. In this example, when somebody unsubscribes, the field ‘newsletter’ is set to ‘no’. Now you can create a newsletter selection to make sure your unsubscribers don't receive any more email.

// dependencies

// change this into your access token
$api = new CopernicaRestAPI("your-access-token", 3);

// data to be sent to the api
$data = array(
    'behavior'      =>  'update',
    'fields'        =>  array('newsletter' => 'no')

// do the call
$api->put("collection/{$collectionID}/unsubscribe", $data);

The example above requires the CopernicaRestApi class.

More information