Appearance
Run the Social monitor now ​
Claims a shared atomic scan lease. With source reddapi, manually scans only Reddit using the saved project ScrapeCreators key, without changing the automatic schedule. Reddit must be enabled with saved queries; requests use at most five pages per query and resume older results across scans. Omit source for the existing scheduled-due monitor run. Quora runs one historical bootstrap, then searches the past week.
Request preparation ​
Send a POST request to /product/sites/{siteId}/social-monitor/run on the appropriate server. Check the API overview for base URL guidance and the server information in the interactive reference. Replace path placeholders with identifiers from the intended account or site; a similarly named record in another workspace is not interchangeable.
The declared request parameters are:
siteId(path, required): Use the type and constraints shown in the parameter reference.
This operation defines an optional request body. Documented media types: application/json. Review required fields, nested objects, and allowed values in the request schema. Keep identifiers and field types intact when replacing example data with your own values.
Authentication and scope ​
The specification lists these security alternatives: BearerAuth, AccessToken. Read any operation-specific restrictions as well: browser-session, account-role, and signed-user requirements may impose additional conditions. See authentication before choosing a credential.
Keep credentials in the appropriate private configuration and remove secrets from shared logs. Confirm the target resource belongs to the intended workflow before issuing a request. Authentication alone should not be treated as confirmation that a supplied account, site, or customer identifier is correct.
Response handling ​
The documented responses for Run the Social monitor now are:
- 200: Run summary
- 400: Invalid source, missing ScrapeCreators key, or Reddit queries not configured
- 404: Not found
- 409: Monitor disabled or a scan is already running
- 429: Monitor cooldown active
Exercise this operation with controlled test data before enabling it in an automated workflow. Validate the request against the schema and inspect the response before updating local state. Do not assume that a successful response means background processing has finished; follow any documented status or follow-up operation when the action queues additional work.
If a connection fails after submission, investigate the current server state before repeating an action whose outcome is uncertain. When requesting support, retain the method, route, response status, and sanitized error message. The interactive reference below provides the detailed schemas and examples for this specific operation.
Run the Social monitor now​
POST
/product/sites/{siteId}/social-monitor/run
Claims a shared atomic scan lease. With source reddapi, manually scans only Reddit using the saved project ScrapeCreators key, without changing the automatic schedule. Reddit must be enabled with saved queries; requests use at most five pages per query and resume older results across scans. Omit source for the existing scheduled-due monitor run. Quora runs one historical bootstrap, then searches the past week.
Authorizations​
BearerAuth
JWT token from login
Type
HTTP (bearer)
or
AccessToken
Personal access token. Value: Token <your-token>
Type
API Key (header: Authorization)
Parameters​
Path Parameters
siteId*
Type
Requiredstring
Request Body​
application/json
JSON"source": "string"
{
 Â
}
Responses​
Run summary
application/json
JSON"ran": true,"monitor": "string","summary": {"scanned": true,"status": "string","created": 0,"duplicates": 0,"skipped": 0,"api_calls": 0,"replies_posted": 0,"errors": ["string"],"opportunities": {"upserted": 0,"ids": ["string"]}}
{
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
 Â
}