Affiliate profile page
const url = 'https://one.optizmo.net/api.cgi?ref=pqmpg&onid=662b824d577c74b57bf1c4fc647b79c7&mailer_id=311111&check_hash=7583f2e660997b8d1c224a8d74260c51&iframe=1&return_format=csv&action=mailer_profile%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&mailer_id=311111&check_hash=7583f2e660997b8d1c224a8d74260c51&iframe=1&return_format=csv&action=mailer_profile%3Fref%3Dpqmpg'Signs the user into SUPPRESS and opens the affiliate’s profile page. The response is a redirect into SUPPRESS,
styled for showing in an iframe; open it in an iframe or a new window as you prefer. iframe is accepted, for
symmetry with Manage Opt-Out Lists, but is not used: this page renders
the same way whether or not you send it.
Values in the check_hash
action, ref, onid, mailer_id.
Failures
In addition to the common failures listed under Sync an advertiser, list, campaign and affiliate:
| Response | Meaning |
|---|---|
failed,Can not find Mailer using mailer_id |
No affiliate in the account has this id. |
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 affiliate.
Example
311111MD5 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
7583f2e660997b8d1c224a8d74260c51Set 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.
Example
failed,Can not find Mailer using mailer_idRedirect to the affiliate’s profile 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" }}