Advertiser and list settings page

GET

/api.cgi?action=client_config

const url = 'https://one.optizmo.net/api.cgi?ref=pqmpg&onid=662b824d577c74b57bf1c4fc647b79c7&advertiser_id=C12412&advertiser_name=BlockBuster&optout_id=f3k93kda3&campaign_id=K3K3&campaign_name=Spring%20Offer&check_hash=84f163e7281cbb63026a5750ef1a7ce8&s=advertiser&return_format=csv&test_only=success&action=client_config%3Fref%3Dpqmpg';
const options = {method: 'GET'};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url 'https://one.optizmo.net/api.cgi?ref=pqmpg&onid=662b824d577c74b57bf1c4fc647b79c7&advertiser_id=C12412&advertiser_name=BlockBuster&optout_id=f3k93kda3&campaign_id=K3K3&campaign_name=Spring%20Offer&check_hash=84f163e7281cbb63026a5750ef1a7ce8&s=advertiser&return_format=csv&test_only=success&action=client_config%3Fref%3Dpqmpg'

Opens a SUPPRESS settings page for the advertiser, to be shown in an iframe or a new window from your platform. The page is rendered by this request itself rather than by a redirect into a SUPPRESS session, so it does not depend on the session cookie described under Embedded pages. The advertiser is created first if it does not exist, exactly as Sync an advertiser, list, campaign and affiliate would. The Opt-Out List named by optout_id must already exist.

The s parameter selects the page:

`s`	Page	Notes
omitted or `advertiser`	Advertiser settings: contact details, which file formats affiliates may download, the opt-out page.	Network accounts only. On an Enterprise account the default page is the list settings.
`optoutlist`	Opt-Out List settings for the list named by `optout_id`.	Requires `optout_id`.
`addEmails`	Upload a file of opt-outs into the list named by `optout_id`.	Requires `optout_id`. Also reachable as `action=add_emails`.

The response is an HTML page. Requests with an unknown s value answer failed,Invalid sub-action.

Values in the `check_hash`

In this order, skipping any parameter you do not send: action, ref, onid, advertiser_id, advertiser_name, optout_id, campaign_id, campaign_name. Do not send optout_name: it is not used, but a sent value is still hashed after optout_id.

Failures

failed,Invalid sub-action above, and the common failures listed under Sync an advertiser, list, campaign and affiliate for creating the advertiser and finding the list.

Parameters

Query Parameters

ref

required

string

<= 5 characters

Your tracking platform’s Reference Code (PRC), issued by Optizmo when the integration was set up.

Example

pqmpg

onid

required

string

The ONID of the SUPPRESS account the request is for. The account holder finds it on the Account Settings page in SUPPRESS under Affiliate Tracking System, and copies it into your platform.

Example

662b824d577c74b57bf1c4fc647b79c7

advertiser_id

required

string

<= 40 characters

Your platform’s id for the advertiser. The advertiser is matched on this id within the account. On an Enterprise account (a single advertiser) the account itself is the advertiser and this id is not used for matching, but it is still required and hashed.

Example

C12412

advertiser_name

required

string

<= 80 characters

Name of the advertiser. Creates the advertiser on first sight and renames it when the name changes. Longer values are truncated.

Example

BlockBuster

optout_id

string

<= 40 characters

The optoutlist_id of a list the advertiser created in SUPPRESS, as returned by Get Opt-Out Lists. The list must exist; send the id exactly as returned.

Required when campaign_id is sent.

Examples

version2

optoutlist_id from Get Opt-Out Lists

f3k93kda3

campaign_id

string

<= 40 characters

Your platform’s id for the campaign (offer). The campaign is created on the list named by optout_id on first sight and matched on this id within the advertiser afterwards. Requires optout_id. Sending an existing campaign with a different optout_id moves the campaign to that list; see Changing a campaign’s Opt-Out List.

Example

K3K3

campaign_name

string

<= 150 characters

Name of the campaign. Required when campaign_id is sent; the campaign is renamed when the name changes. Longer values are truncated.

Example

Spring Offer

check_hash

required

string

/^[0-9a-f]{32}$/

MD5 hex digest of the request’s hashed values, in the order they are listed for this action, followed by your Access Key (PAK). See Authentication for the rules and a worked example.

Examples

version2

The client_sync example under Authentication

84f163e7281cbb63026a5750ef1a7ce8

string

Allowed values: advertiser optoutlist addEmails

The page to open. Not hashed.

advertiser_email

string

<= 80 characters

Contact email stored on the advertiser. Not hashed.

advertiser_phone

string

<= 20 characters

Contact phone number stored on the advertiser. Not hashed.

advertiser_contact

string

<= 70 characters

Contact name stored on the advertiser. Not hashed.

return_format

string

default: csv

Allowed values: csv xml json

Sets the format of the success or failed answer on the synchronisation and status actions, and of the failure answer on every action. It does not change the success answer of the report and list actions, which is always their own XML document, or of the actions that answer with a page or a redirect. csv, xml and json are the only recognised values; anything else is answered in the csv format, the default. Not included in the check_hash.

test_only

string

Allowed values: success failed

Only honoured by Sync an advertiser, list, campaign and affiliate, Sync onto a linked list, Generate an SMAK, Account report, Get Opt-Out Lists, Advertiser and list settings page and Add opt-outs page; every other action ignores it and runs as normal, so sending it there does not stop the real change. On the actions that honour it, once the request has authenticated, it answers without creating or changing anything, and before the page renders on the two pages actions: failed,Test Failed Output for test_only=failed everywhere it is honoured. For test_only=success: the sync actions return a fixed key pair (https://TESTONLY.optizmo.net/m-test-a00-410324axc3e1eb7a and https://TESTONLY.optoutsystem.net/o-test-a00-546c4dxa10df19b8) in place of real ones, in the same body shape a real success with keys would have; the account report returns that same fixed key pair, not a report document; Get Opt-Out Lists returns a fixed two-entry list document; and the two pages actions return a bare success with no keys, the same shape as a real one with no campaign_id/mailer_id pair. Not included in the check_hash.

Responses

200

The requested settings page, or a failure in the format selected by return_format.

string

Example

failed,Invalid sub-action

503

The system is in maintenance mode. Retry later. The answer follows return_format: csv (also the answer to a return_format that is neither xml nor json) as text/plain, xml as text/xml, json as application/json.

string

Example

failed,System currently under maintenance

string

Example

<?xml version="1.0" encoding="utf-8"?>
<output><result>failed</result>
<error>System currently under maintenance</error></output>

object

output

object

result

required

string

Allowed values: success failed

data

Present when result is success. This action issues no keys, so both values are null.

object

mailer_url

string

nullable

optout_url

string

nullable

error

Present when result is failed.

string

Example

{
  "output": {
    "result": "failed",
    "error": "System currently under maintenance"
  }
}

Advertiser and list settings page

Values in the check_hash

Failures

Parameters

Query Parameters

Example

Example

Example

Example

Examples

Example

Example

Examples

Responses

200

Example

503

Example

Example

Example

Values in the `check_hash`