Skip to content
URL:
https://<root>/system/indexer/status/mismatch
Methods:
GET
Version Introduced:
11.5

Access requirements

Required privileges

The Enterprise Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.


Tokens

This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Enterprise Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.

Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generateToken operation in the Enterprise Directory API. For security reasons, all POST requests made to the Enterprise Administrator API must include a token in the request body.


Learn how to generate a token

Description

The mismatch operation returns whether there is a discrepancy between an organization's users, groups, and items in the database and the index. If all content is present in both the database and the index, the operation returns a success response. If there are discrepancies between the database and the index, the operation's response returns arrays that contain the index count, the database count, the IDs of the content missing from the index, and the IDs of the content missing from the database.

Request parameters

ParameterDetails

f

The response format. The default format is html.

Values: html | json | pjson

Example usage

The following is a sample request URL for the mismatch operation:

Use dark colors for code blocksCopy
1
https://organization.example.com/<context>/admin/system/indexer/status/mismatch?f=pjson

JSON Response examples

Use dark colors for code blocksCopy
1
2
3
4
{
  "message": "No index mismatch found.",
  "status": "success"
}

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.