Navigation

Get All Atlas Search Indexes for a Collection

On this page

  • Required Roles
  • Resource
  • Request Parameters
  • Request Path Parameters
  • Request Query Parameters
  • Request Body Parameters
  • Response Elements
  • Example Request
  • Example Response
  • Response Header
  • Response Body

The fts resource allows you to retrieve and edit Atlas Search analyzers and index configurations for the specified cluster.

The Atlas API authenticates using HTTP Digest Authentication. Provide a programmatic API public key and corresponding private key as the username and password when constructing the HTTP request. To learn how to configure API access for an Atlas project, see Configure Atlas API Access.

Note

Groups and projects are synonymous terms. Your {GROUP-ID} is the same as your project ID. For existing groups, your group/project ID remains the same. The resource and corresponding endpoints use the term groups.

You must have the:

Base URL: https://cloud.mongodb.com/api/atlas/v1.0

GET /groups/{GROUP-ID}/clusters/{CLUSTER-NAME}/fts/indexes/{DATABASE-NAME}/{COLLECTION-NAME}
Path Element
Type
Necessity
Description
GROUP-ID
string
Required
Unique identifier for the project that contains the specified cluster.
CLUSTER-NAME
string
Required
Name of the cluster containing the collection with one or more Atlas Search indexes.
DATABASE-NAME
string
Required
Name of the database containing the collection with one or more Atlas Search indexes.
COLLECTION-NAME
string
Required
Name of the collection with one or more Atlas Search indexes.

This endpoint may use any of the HTTP request query parameters available to all Atlas API resources. These are all optional.

Name
Type
Necessity
Description
Default
pageNum
integer
Optional
Page number, starting with one, that Atlas returns of the total number of objects.
1
itemsPerPage
integer
Optional
Number of items that Atlas returns per page, up to a maximum of 500.
100
includeCount
boolean
Optional
Flag that indicates whether Atlas returns the totalCount parameter in the response body.
true
pretty
boolean
Optional
Flag that indicates whether Atlas returns the JSON response in the prettyprint format.
false
envelope
boolean
Optional

Flag that indicates whether Atlas wraps the response in an envelope.

Some API clients cannot access the HTTP response headers or status code. To remediate this, set envelope=true in the query.

Endpoints that return a list of results use the results object as an envelope. Atlas adds the status parameter to the response body.

false

This endpoint doesn't use HTTP request body parameters.

The HTTP response returns a JSON document that includes an array of index definitions. Each index definition contains the following elements:

Name
Type
Description
analyzer
Optional
Analyzer used when creating the index.
analyzers
Optional
Custom analyzers used in this index.
collectionName
string
Name of the collection the index is on.
database
string
Name of the database the collection is in.
indexID
string
Unique identifier for the index.
mappings
object
Object containing index specifications for the collection fields.
mappings
.dynamic
boolean
Flag indicating whether the index uses dynamic or static mappings.
mappings
.fields
object
Object containing one or more field specifications.
name
string
Name of the index.
searchAnalyzer
string
Analyzer to use when searching the index.
status
string

Status of the index. Value can be one of the following statuses:

  • IN_PROGRESS - Atlas is building or re-building the index after an edit.
  • STEADY - Index is ready to use.
  • FAILED - Atlas could not build the index.
  • MIGRATING - Atlas cluster tier is being upgraded and indexes are migrating.
synonyms
array of documents
Synonyms mapping definition used in this index.
synonyms[i]
.analyzer
string
Name of the analyzer used in this synonym mapping. If mappings.dynamic is true, Atlas Search uses the default analyzer, lucene.standard, for synonym mapping.
synonyms[i]
.name
string
Name of the synonym mapping.
synonyms[i]
.source
document
Collection details for this synonym mapping definition.
synonyms[i]
.source
.collection
string
Name of the source MongoDB collection for the synonyms.
curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest \
--include \
--request GET "https://cloud.mongodb.com/api/atlas/v1.0/groups/{GROUP-ID}/clusters/{CLUSTER-NAME}/fts/indexes/{DATABASE-NAME}/{COLLECTION-NAME}?pretty=true"
HTTP/1.1 401 Unauthorized
Content-Type: application/json;charset=ISO-8859-1
Date: {dateInUnixFormat}
WWW-Authenticate: Digest realm="MMS Public API", domain="", nonce="{nonce}", algorithm=MD5, op="auth", stale=false
Content-Length: {requestLengthInBytes}
Connection: keep-alive
HTTP/1.1 200 OK
Vary: Accept-Encoding
Content-Type: application/json
Strict-Transport-Security: max-age=300
Date: {dateInUnixFormat}
Connection: keep-alive
Content-Length: {requestLengthInBytes}

The following example response contains an array of two index definitions.

The first has the following characteristics:

  • It is the default definition, which indexes all text fields dynamically and works with any collection.
  • It is named default.

The second definition has the following characteristics:

  • It is a custom definition with static mappings for two fields named genres and plot.
  • It is named SearchIndex1.
[
{
"collectionName" : "movies",
"database" : "sample_mflix",
"indexID" : "5d114a3587d9d65de99e7371",
"mappings" : {
"dynamic" : true
},
"name" : "default"
},
{
"collectionName" : "movies",
"database" : "sample_mflix",
"indexID" : "5d1268a980eef518dac0cf41",
"mappings" : {
"dynamic" : false,
"fields" : {
"genres" : {
"analyzer" : "lucene.standard",
"type" : "string"
},
"plot" : {
"analyzer" : "lucene.standard",
"type" : "string"
}
}
},
"name" : "SearchIndex1",
"status": "STEADY"
}
]
Give Feedback

On this page

  • Required Roles
  • Resource
  • Request Parameters
  • Request Path Parameters
  • Request Query Parameters
  • Request Body Parameters
  • Response Elements
  • Example Request
  • Example Response
  • Response Header
  • Response Body