# Get multiple term vectors


**POST /{index}/_mtermvectors**

**All methods and paths for this operation:**

<div>
                      <span class="operation-verb get">GET</span>
                      <span class="operation-path">/_mtermvectors</span>
                      </div>
                    <div>
                      <span class="operation-verb post">POST</span>
                      <span class="operation-path">/_mtermvectors</span>
                      </div>
                    <div>
                      <span class="operation-verb get">GET</span>
                      <span class="operation-path">/{index}/_mtermvectors</span>
                      </div>
                    <div>
                      <span class="operation-verb post">POST</span>
                      <span class="operation-path">/{index}/_mtermvectors</span>
                      </div>
                    

Get multiple term vectors with a single request.
You can specify existing documents by index and ID or provide artificial documents in the body of the request.
You can specify the index in the request body or request URI.
The response contains a `docs` array with all the fetched termvectors.
Each element has the structure provided by the termvectors API.

**Artificial documents**

You can also use `mtermvectors` to generate term vectors for artificial documents provided in the body of the request.
The mapping used is determined by the specified `_index`.

## Required authorization

* Index privileges: `read`



## Servers
- http://api.example.com: http://api.example.com ()


## Authentication methods
- Api key auth
- Basic auth
- Bearer auth


## Parameters

### Path parameters
- **index** (string)
  The name of the index that contains the documents.

### Query parameters
- **ids** (array[string])
  A comma-separated list of documents ids. You must define ids as parameter or set "ids" or "docs" in the request body
- **fields** (string | array[string])
  A comma-separated list or wildcard expressions of fields to include in the statistics.
  It is used as the default list unless a specific field list is provided in the `completion_fields` or `fielddata_fields` parameters.
- **field_statistics** (boolean)
  If `true`, the response includes the document count, sum of document frequencies, and sum of total term frequencies.
- **offsets** (boolean)
  If `true`, the response includes term offsets.
- **payloads** (boolean)
  If `true`, the response includes term payloads.
- **positions** (boolean)
  If `true`, the response includes term positions.
- **preference** (string)
  The node or shard the operation should be performed on.
  It is random by default.
- **realtime** (boolean)
  If true, the request is real-time as opposed to near-real-time.
- **routing** (string | array[string])
  A custom value used to route operations to a specific shard.
- **term_statistics** (boolean)
  If true, the response includes term frequency and document frequency.
- **version** (number)
  If `true`, returns the document version as part of a hit.
- **version_type** (string)
  The version type.

  Supported values include:
    - `internal`: Use internal versioning that starts at 1 and increments with each update or delete.
    - `external`: Only index the document if the specified version is strictly higher than the version of the stored document or if there is no existing document.
    - `external_gte`: Only index the document if the specified version is equal or higher than the version of the stored document or if there is no existing document.
  NOTE: The `external_gte` version type is meant for special use cases and should be used with care.
  If used incorrectly, it can result in loss of data.


### Body: application/json (object)

- **docs** (array[object])
  An array of existing or artificial documents.
- **ids** (array[string])
  A simplified syntax to specify documents by their ID if they're in the same index.


## Responses
### 200


#### Body: application/json (object)
- **docs** (array[object])



[Powered by Bump.sh](https://bump.sh)