[Yandex Cloud documentation](../../../index.md) > [Yandex API Gateway](../../index.md) > [Concepts](../index.md) > [Specification extensions](index.md) > Integration options > Static response

# x-yc-apigateway-integration:dummy extension

The `x-yc-apigateway-integration:dummy` extension returns fixed content with the specified response code and required headers without any third-party service involved.

You can add an extension to a specification using the [specification constructor](../../operations/spec-constructor/index.md).

## Supported parameters {#parameters}

The table below lists the parameters specific to API Gateway API gateways. You can find the description of other parameters in the [OpenAPI 3.0 specification](https://github.com/OAI/OpenAPI-Specification).

Parameter | Type | Description 
----|----|----
`http_code` | `int` | HTTP response code.
`http_headers` | `map[string](string\|[]string)` | It shows the list of headers to send in the response. The parameters are subsituted into `http_headers`.
`content` | `map[string]string` | Data to send in response. <br>It can be either actual content or the result of mapping the requested `Content-Type` to data. This allows you to send errors in the requested format: JSON or XML. The `*` key is used for the default value. The parameters are subsituted into `content`.

## Extension specification {#spec}

Specification example: 

```yaml
x-yc-apigateway-integration:
  type: dummy
  http_code: 302
  http_headers:
    Location: "/some/location"
    Set-Cookie: ["a={number}", "b=2"]
  content:
    "application/json": "{ \"message\": \"You've been redirected.\" }"
```

Extension features:
* If the request contains the `Accept` header:
    * The best match is selected first.
    * If there is no match, the `*` key is selected.
    * If there is no key, the `415 Media not supported` response is returned. 
* If the `Accept` header is missing, any response may be selected.
* If the content option is selected by the `*` key, the response's `Content-Type` will be picked from `http_headers`. If it is not specified there, the actual `Content-Type` is returned.


## Use cases {#examples}

* [Protecting API Gateway by integrating with Smart Web Security](../../tutorials/api-gw-sws-integration.md)
* [Working with an API gateway via WebSocket](../../tutorials/api-gw-websocket.md)
* [How to create a Slack chat bot](../../tutorials/slack-bot-serverless.md)