---
title: Term query
description: Returns documents that contain an exact term in a provided field. You can use the term query to find documents based on a precise value such as a price,...
url: https://www.elastic.co/elastic/docs-builder/docs/3028/reference/query-languages/query-dsl/query-dsl-term-query
products:
  - Elasticsearch
---

# Term query
Returns documents that contain an **exact** term in a provided field.
You can use the `term` query to find documents based on a precise value such as a price, a product ID, or a username.
<warning>
  Avoid using the `term` query for [`text`](https://www.elastic.co/elastic/docs-builder/docs/3028/reference/elasticsearch/mapping-reference/text) fields.By default, Elasticsearch changes the values of `text` fields as part of [analysis](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/3028/manage-data/data-store/text-analysis). This can make finding exact matches for `text` field values difficult.To search `text` field values, use the [`match`](https://www.elastic.co/elastic/docs-builder/docs/3028/reference/query-languages/query-dsl/query-dsl-match-query) query instead.
</warning>


## Example request

```json

{
  "query": {
    "term": {
      "user.id": {
        "value": "kimchy",
        "boost": 1.0
      }
    }
  }
}
```


## Top-level parameters for `term`

<definitions>
  <definition term="<field>">
    (Required, object) Field you wish to search.
  </definition>
</definitions>


## Parameters for `<field>`

<definitions>
  <definition term="value">
    (Required, string) Term you wish to find in the provided `<field>`. To return a document, the term must exactly match the field value, including whitespace and capitalization.
  </definition>
  <definition term="boost">
    (Optional, float) Floating point number used to decrease or increase the [relevance scores](/elastic/docs-builder/docs/3028/reference/query-languages/query-dsl/query-filter-context#relevance-scores) of a query. Defaults to `1.0`.
    You can use the `boost` parameter to adjust relevance scores for searches containing two or more queries.
    Boost values are relative to the default value of `1.0`. A boost value between `0` and `1.0` decreases the relevance score. A value greater than `1.0` increases the relevance score.
  </definition>
  <definition term="case_insensitive">
    <admonition title="Added in 7.10.0">
      This parameter was added in 7.10.0.
    </admonition>
    (Optional, Boolean) Allows ASCII case insensitive matching of the value with the indexed field values when set to true. Default is false which means the case sensitivity of matching depends on the underlying field’s mapping.
  </definition>
</definitions>


## Notes


### Avoid using the `term` query for `text` fields

By default, Elasticsearch changes the values of `text` fields during analysis. For example, the default [standard analyzer](https://www.elastic.co/elastic/docs-builder/docs/3028/reference/text-analysis/analysis-standard-analyzer) changes `text` field values as follows:
- Removes most punctuation
- Divides the remaining content into individual words, called [tokens](https://www.elastic.co/elastic/docs-builder/docs/3028/reference/text-analysis/tokenizer-reference)
- Lowercases the tokens

To better search `text` fields, the `match` query also analyzes your provided search term before performing a search. This means the `match` query can search `text` fields for analyzed tokens rather than an exact term.
The `term` query does **not** analyze the search term. The `term` query only searches for the **exact** term you provide. This means the `term` query may return poor or no results when searching `text` fields.
To see the difference in search results, try the following example.
1. Create an index with a `text` field called `full_text`.
   ```json

   {
     "mappings": {
       "properties": {
         "full_text": { "type": "text" }
       }
     }
   }
   ```
2. Index a document with a value of `Quick Brown Foxes!` in the `full_text` field.
   ```json

   {
     "full_text":   "Quick Brown Foxes!"
   }
   ```
   
   Because `full_text` is a `text` field, Elasticsearch changes `Quick Brown Foxes!` to `[quick, brown, fox]` during analysis.
3. Use the `term` query to search for `Quick Brown Foxes!` in the `full_text` field. Include the `pretty` parameter so the response is more readable.
   ```json

   {
     "query": {
       "term": {
         "full_text": "Quick Brown Foxes!"
       }
     }
   }
   ```
   
   Because the `full_text` field no longer contains the **exact** term `Quick Brown Foxes!`, the `term` query search returns no results.
4. Use the `match` query to search for `Quick Brown Foxes!` in the `full_text` field.
   
   ```json

   {
     "query": {
       "match": {
         "full_text": "Quick Brown Foxes!"
       }
     }
   }
   ```
   
   Unlike the `term` query, the `match` query analyzes your provided search term, `Quick Brown Foxes!`, before performing a search. The `match` query then returns any documents containing the `quick`, `brown`, or `fox` tokens in the `full_text` field.
   Here’s the response for the `match` query search containing the indexed document in the results.
   ```json
   {
     "took": 1,
     "timed_out": false,
     "_shards": {
       "total": 1,
       "successful": 1,
       "skipped": 0,
       "failed": 0
     },
     "hits": {
       "total": {
         "value": 1,
         "relation": "eq"
       },
       "max_score": 0.8630463,
       "hits": [
         {
           "_index": "my-index-000001",
           "_id": "1",
           "_score": 0.8630463,
           "_source": {
             "full_text": "Quick Brown Foxes!"
           }
         }
       ]
     }
   }
   ```