Managani Docs

Appearance

List Social monitor signals ​

Returns semantically scored Social signals ordered by score descending, then newest first. The default view contains active review signals; lifecycle statuses remain available through the status filter.

Request preparation ​

Send a GET request to /product/sites/{siteId}/social-signals 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.
  • status (query, optional): Use the type and constraints shown in the parameter reference.
  • source (query, optional): Use the type and constraints shown in the parameter reference.
  • include_zero (query, optional): Include legacy unscored signals. Low semantically scored signals are always included.

No request body is declared in the current specification. Check the route and any documented parameters before sending the request rather than adding an arbitrary JSON payload.

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 List Social monitor signals are:

  • 200: OK

Begin with a known record or a narrow query and inspect the returned fields before displaying them to users. Where the operation defines pagination, follow those parameters to retrieve additional results. An empty successful response is different from a failed request; keep errors visible to the calling workflow instead of presenting them as an empty data set.

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.

List Social monitor signals​

GET
/product/sites/{siteId}/social-signals

Returns semantically scored Social signals ordered by score descending, then newest first. The default view contains active review signals; lifecycle statuses remain available through the status filter.

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
string
Required

Query Parameters

status
Type
string
Valid values
"new""queued""scheduled""drafted""actioned""dismissed""failed"
source
Type
string
Valid values
"reddapi""quora""bluesky""linkedin""web"
include_zero

Include legacy unscored signals. Low semantically scored signals are always included.

Type
string
Valid values
"1""true"

Responses​

OK

application/json
JSON
{
  
"signals": [
  
],
  
"counts": {
  
},
  
"sourceCounts": {
  
}
}

Playground​

Authorization
Variables
Key
Value

Samples​

Powered by VitePress OpenAPI