Skip to content

Latest commit

 

History

History
57 lines (41 loc) · 1.94 KB

rest-put-database-unsubscribe.md

File metadata and controls

57 lines (41 loc) · 1.94 KB
Raw

REST API: PUT database unsubscribe

For every database, you can set the unsubscribe algorithm separately. When Copernica’s servers receive an unsubscription the unsubscribe behaviour 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:

https://api.copernica.com/v2/database/$id/unsubscribe?access_token=xxxx

In this, the variable $id has to be replaced by the numerical identifier of the database 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 data 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’)

The parameter ‘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.

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’. You could use this field in a newsletter selection.

// dependencies
require_once('copernica-rest-api.php');

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

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

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

The example above requires the CopernicaRestApi class.

More information