---
type: api
title: Update the connector is_native flag
url: https://www.elastic.co/elastic/docs-builder/docs/4493/api/doc/elasticsearch/operation/operation-connector-update-native
resource: https://www.elastic.co/elastic/docs-builder/docs/4493/api/doc/elasticsearch/operation/operation-connector-update-native
products:
  - Elasticsearch
---

# Update the connector is_native flag

Availability: Beta since 8.12

## Paths

- `PUT` `/_connector/{connector_id}/_native`

#### Path parameters

- `connector_id` (string) — required
  The unique identifier of the connector to be updated

## Authentication

- Api key: `Authorization: <value>`
  Elasticsearch APIs support key-based authentication.
  You must create an API key and use the encoded value in the request header.
  For example:
  
  
  ```
  curl -X GET "${ES_URL}/_cat/indices?v=true" \
    -H "Authorization: ApiKey ${API_KEY}"
  ```
  
  To get API keys, use the `/_security/api_key` APIs.
- Basic: `Authorization: Basic <credentials>`
- Bearer: `Authorization: Bearer <token>`
  Elasticsearch APIs support the use of bearer tokens in the `Authorization` HTTP header to authenticate with the API.
  For examples, refer to [Token-based authentication services](https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/token-based-authentication-services)

## Request body

`application/json`

- `is_native` (boolean) — required

## Response

`application/json`

- `result` (enum)
  Values: `created`, `updated`, `deleted`, `not_found`, `noop`
## Code examples

#### Console

```console
PUT /_connector/CONNECTOR_ID/_native
{
  "is_native": false
}
```

#### curl

```curl
curl -X PUT "${ELASTICSEARCH_URL}/_connector/${CONNECTOR_ID}/_native" \
  -H "Authorization: ApiKey ${API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "is_native": false
  }'
```