Title: Process SiteLock Threat Notifications Using the API  
PrimaryCategory: SiteLock  
Type: Procedural  
Tags: SiteLock, API, threat_notifications, processing, reseller_id  
Source UI Terms: auth-userid, api-key, notification-id, reseller-id, POST  
Source Reference: Process SiteLock Threat Notifications Using the API  

Prerequisites:
- Have your API authentication credentials: auth-userid (Integer) and api-key (String).
- Identify the notification-id(s) (Array of Integers) of the threat notifications to process.
- (Optional) Know the reseller-id (Integer) if processing notifications for a specific reseller.

Steps:
1) Prepare a POST API request to the endpoint:  
   `https://test.httpapi.com/api/sitelock/threat/processed.json`
2) Include the following parameters as query strings or in the request body:  
   - auth-userid (Required): Your integer user ID for authentication.  
   - api-key (Required): Your API key string for authentication.  
   - notification-id (Required): Array of integers representing the threat notification IDs to mark as processed.  
   - reseller-id (Optional): Integer reseller ID if processing notifications on behalf of a reseller; otherwise, defaults to the current user.  
3) Send the POST request to the API endpoint with the parameters.
4) Check the response:  
   - If successful, the API returns the string `&quot;true&quot;`.  
   - If an error occurs, a JSON object with a key `&quot;status&quot;` set to `&quot;ERROR&quot;` and an error message will be returned.

Summary:  
Use the SiteLock API with required authentication and notification IDs to mark threat notifications as processed, optionally specifying a reseller ID if applicable.

Evaluation Pairs:  
Q1: What parameters are required to process a SiteLock threat notification via API?  
A1: You must provide auth-userid (Integer), api-key (String), and notification-id (Array of Integers) parameters.  

Q2: How do you process threat notifications for a reseller using the SiteLock API?  
A2: Include the optional reseller-id parameter with the reseller&#39;s integer ID to process their threat notifications.  

Q3: What indicates a successful processing response from the SiteLock API?  
A3: The API returns the string &quot;true&quot; if the threat notifications are processed successfully.

<p>When you want to mark SiteLock threat notifications as processed using the API. This article explains the required parameters, reseller scope handling, API request format, and response behavior for threat notification processing.</p>
<div class="region region-content">
<div class="block block-core block-page-title-block" id="block-twostates-page-title">
<div class="content">
<h1 class="title page-title"><span class="field field--name-title field--type-string field--label-hidden">Process Threat Notifications</span><a href="/help/article/answer/2131#heading_0" target="_blank"></a></h1>
</div>
</div>
<div class="node__content clearfix">
<div class="layout layout--onecol">
<div class="layout__region layout__region--content">
<div class="clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__item">
<h2><a name="heading_0"></a>Description</h2>
<p>Processes the specified threat notifications.</p>
<h2><a name="heading_1"></a>Parameters</h2>
<table class="codetable"><tbody><tr><th colspan="1" rowspan="1">Name</th><th colspan="1" rowspan="1">Data Type</th><th colspan="1" rowspan="1">Required / Optional</th><th colspan="1" rowspan="1">Description</th></tr><tr><td colspan="1" rowspan="1">auth-userid</td><td colspan="1" rowspan="1">Integer</td><td colspan="1" rowspan="1">Required</td><td colspan="1" rowspan="1">Authentication Parameter</td></tr><tr><td colspan="1" rowspan="1">api-key</td><td colspan="1" rowspan="1">String</td><td colspan="1" rowspan="1">Required</td><td colspan="1" rowspan="1">Authentication Parameter</td></tr><tr><td colspan="1" rowspan="1">notification-id</td><td colspan="1" rowspan="1">Array of Integers</td><td colspan="1" rowspan="1">Required</td><td colspan="1" rowspan="1">Notification ID of the threat notifications which needs to be processed. Use this method to get the Notification ID(s).</td></tr><tr><td colspan="1" rowspan="1">reseller-id</td><td colspan="1" rowspan="1">Integer</td><td colspan="1" rowspan="1">Optional</td><td colspan="1" rowspan="1"><strong>Reseller ID</strong> of the Reseller for whom threat notifications are to be processed. By default, threat notifications for the current user will be processed.</td></tr></tbody></table>
<h2><a name="heading_2"></a>HTTP Method</h2>
<p>POST</p>
<h2><a name="heading_3"></a>Example Test URL Request</h2>
<p><code>https://test.httpapi.com/api/sitelock/threat/processed.json?auth-userid=0&amp;api-key=key&amp;notification-id=0 </code></p>
<h2><a name="heading_4"></a>Response</h2>
<p>Returns <em>true</em> (String) if the threat notification(s) is/are processed successfully.</p>
<p>In case of any errors, a <strong>status</strong> key with value as <em>ERROR</em> alongwith an error message will be returned.</p>
</div>
</div>
</div>
</div>
<div class="mychild-topics"> </div>
</div>
<div class="seedetailssection"> </div>

When you want to mark SiteLock threat notifications as processed using the API. This article explains the required parameters, reseller scope handling, API request format, and response behavior for threat notification processing.

Name	Data Type	Required / Optional	Description
auth-userid	Integer	Required	Authentication Parameter
api-key	String	Required	Authentication Parameter
notification-id	Array of Integers	Required	Notification ID of the threat notifications which needs to be processed. Use this method to get the Notification ID(s).
reseller-id	Integer	Optional	Reseller ID of the Reseller for whom threat notifications are to be processed. By default, threat notifications for the current user will be processed.