Skip to content

Rebuild Managani search indexes ​

Recreates the URL, crawled-page, feedback, feedback-comment, and release indexes. Active crawl-enabled project sites are queued for a full recrawl.

Request preparation ​

Send a POST request to /reindex 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.

No separate path or query parameters are declared for this operation in the current specification. Do not invent filtering or pagination options from another endpoint; use only the contract shown here.

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 Rebuild Managani search indexes are:

  • 200: OK
  • 403: Account admin access required

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.

Rebuild Managani search indexes​

POST
/reindex

Recreates the URL, crawled-page, feedback, feedback-comment, and release indexes. Active crawl-enabled project sites are queued for a full recrawl.

Authorizations​

BearerAuth

JWT token from login

Type
HTTP (bearer)
or
AccessToken

Personal access token. Value: Token <your-token>

Type
API Key (header: Authorization)

Responses​

OK

application/json
JSON
{
  
"status": "string",
  
"message": "string",
  
"total_queued": 0,
  
"indexed": 0,
  
"remaining": 0,
  
"started_at": "string",
  
"counts": {
  
  
"db_records": 0,
  
  
"indexed_records": 0,
  
  
"not_indexed_records": 0,
  
  
"by_type": {
  
  
  
"pages": {
  
  
  
  
"db_records": 0,
  
  
  
  
"indexed_records": 0,
  
  
  
  
"not_indexed_records": 0
  
  
  
},
  
  
  
"additionalProperties": {
  
  
  
  
"db_records": 0,
  
  
  
  
"indexed_records": 0,
  
  
  
  
"not_indexed_records": 0
  
  
  
}
  
  
}
  
},
  
"results": {
  
  
"urls": {
  
  
  
"queued": 0
  
  
},
  
  
"pages": {
  
  
  
"queued": 0,
  
  
  
"sources": 0
  
  
},
  
  
"feedback": {
  
  
  
"queued": 0
  
  
},
  
  
"feedback_comments": {
  
  
  
"queued": 0
  
  
},
  
  
"releases": {
  
  
  
"queued": 0
  
  
}
  
},
  
"sources": [
  
  
{
  
  
  
"source_id": "string",
  
  
  
"site_id": "string",
  
  
  
"url": "string",
  
  
  
"title": "string",
  
  
  
"status": "string",
  
  
  
"indexed_pages_count": 0,
  
  
  
"stored_indexed_pages_count": 0,
  
  
  
"count_mismatch": true
  
  
}
  
]
}

Playground​

Authorization

Samples​

Powered by VitePress OpenAPI