code: def search_template(self, index=None, body=None, params=None):
          
          return self.transport.perform_request(
              "GET", _make_path(index, "_search", "template"), params=params, body=body
          )
docs: A query that accepts a query template and a map of key/value pairs to
          fill in template parameters.
          `<http://www.elastic.co/guide/en/elasticsearch/reference/current/search-template.html>`_
  
          :arg index: A list of index names to search, or a string containing a
              comma-separated list of index names to search; use `_all` or the
              empty string to perform the operation on all indices
          :arg body: The search definition template and its params
          :arg allow_no_indices: Whether to ignore if a wildcard indices
              expression resolves into no concrete indices. (This includes `_all`
              string or when no indices have been specified)
          :arg expand_wildcards: Whether to expand wildcard expression to concrete
              indices that are open, closed or both., default 'open', valid
              choices are: 'open', 'closed', 'none', 'all'
          :arg explain: Specify whether to return detailed information about score
              computation as part of a hit
          :arg ignore_unavailable: Whether specified concrete indices should be
              ignored when unavailable (missing or closed)
          :arg preference: Specify the node or shard the operation should be
              performed on (default: random)
          :arg profile: Specify whether to profile the query execution
          :arg routing: A comma-separated list of specific routing values
          :arg scroll: Specify how long a consistent view of the index should be
              maintained for scrolled search
          :arg search_type: Search operation type, valid choices are:
              'query_then_fetch', 'query_and_fetch', 'dfs_query_then_fetch',
              'dfs_query_and_fetch'
          :arg typed_keys: Specify whether aggregation and suggester names should
              be prefixed by their respective types in the response