Manage Opt-Out Lists
const url = 'https://one.optizmo.net/api.cgi?ref=pqmpg&onid=662b824d577c74b57bf1c4fc647b79c7&advertiser_id=C12412&advertiser_name=BlockBuster&check_hash=7583f2e660997b8d1c224a8d74260c51&iframe=1&return_format=csv&action=manage_optoutlists%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&check_hash=7583f2e660997b8d1c224a8d74260c51&iframe=1&return_format=csv&action=manage_optoutlists%3Fref%3Dpqmpg'Signs the user into SUPPRESS, scoped to the advertiser, and opens the Opt-Out Lists page where the advertiser creates and manages its lists. This is the version 2 workflow: lists are created here, and your platform then offers them for selection through Get Opt-Out Lists. Version 1 platforms create lists through client_sync instead.
The advertiser is created first if it does not exist. The response is a redirect into SUPPRESS; open it in an
iframe (send iframe=1) or a new window.
Values in the check_hash
action, ref, onid, advertiser_id, advertiser_name.
Failures
The common failures listed under Sync an advertiser, list, campaign and affiliate, for creating the advertiser.
Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters”Your tracking platform’s Reference Code (PRC), issued by Optizmo when the integration was set up.
Example
pqmpgThe 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
662b824d577c74b57bf1c4fc647b79c7Your 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
C12412Name of the advertiser. Creates the advertiser on first sight and renames it when the name changes. Longer values are truncated.
Example
BlockBusterMD5 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.
Example
7583f2e660997b8d1c224a8d74260c51Contact email stored on the advertiser. Not hashed.
Contact phone number stored on the advertiser. Not hashed.
Contact name stored on the advertiser. Not hashed.
Set to 1 when the page is shown inside an iframe in your platform. Not hashed.
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.
Responses
Section titled “ Responses ”A failure in the format selected by return_format, or a sign-in page for browsers that block third-party cookies.
Example
failed,Check Hash Failed.Redirect to the Opt-Out Lists page in SUPPRESS, signed in.
Headers
Section titled “Headers”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.
Example
failed,System currently under maintenanceExample
<?xml version="1.0" encoding="utf-8"?><output><result>failed</result><error>System currently under maintenance</error></output>object
object
Present when result is success. This action issues no keys, so both values are null.
object
Present when result is failed.
Example
{ "output": { "result": "failed", "error": "System currently under maintenance" }}