---
title: "Update ELT Destination"
method: POST
path: "/elt_destinations/{id}"
tags: ["ELT Destinations"]
---

# Update ELT Destination

`POST /elt_destinations/{id}`

## Request

- Base URL: `https://connect.weld.app`
- URL: `https://connect.weld.app/elt_destinations/{id}`
- Auth: API key in header `x-api-key`

Beta. Update the label, the settings, or whether new ELT Syncs load into an ELT Destination. While an ELT Sync loads into it, its settings cannot change.

## Path parameters

- `id` string, required

## Request body

- EltDestinationUpdateRequestDto
  - `label` string, nullable: Names the ELT Destination. Unique among the account's ELT Destinations. Left out, the label stays as it is.
  - `settings` object: The ELT Destination's settings, answering the schema from GET /elt_destinations/settings_schema for its Connection. A setting the schema gives a default may be left out and takes that default. Left out, the settings stay as they are. Refused while an ELT Sync loads into the destination, unless they are unchanged.
  - `use_for_new_syncs` boolean: Whether ELT Syncs created without `additional_destinations` also load into this ELT Destination. ELT Syncs that already exist are not changed. Refused when another ELT Destination on the same Connection already is. Left out, it stays as it is.

## Response `200`

- EltDestinationDto
  - `id` string, required: The ID of the ELT Destination.
  - `label` string, required: Names the ELT Destination. Unique among the account's ELT Destinations.
  - `connection_id` string, required: The ID of the Connection the ELT Destination loads into.
  - `integration_id` string, required: The integration of the Connection.
  - `settings` object, required: The ELT Destination's settings, answering the schema from GET /elt_destinations/settings_schema for its Connection. Empty when the integration's schema has no properties, or the destination was added before it had one.
  - `use_for_new_syncs` boolean, required: Whether ELT Syncs created without `additional_destinations` also load into this ELT Destination. ELT Syncs that already exist are not changed.
  - `history_tables_supported` boolean, required: Whether this destination keeps a history table for a stream.
  - `soft_deletes_supported` boolean, required: Whether full syncs into this destination can keep the rows the source no longer returns.
  - `cdc_deletes_supported` boolean, required: Whether this destination applies the deletes a Postgres change data capture run reports.
  - `created_at` string, date-time, required: When the ELT Destination was added.

## Other responses

- `400`: The label is taken, the settings do not answer the settings schema or change while an ELT Sync loads into the destination, or another ELT Destination on the same Connection is already used for new ELT Syncs.
- `403`: The account does not have the multi-destination ELT feature.
- `404`: ELT Destination not found.

## Changes

- **2026-10-26** `1f8c53229872`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/weld/apis/weld-rest-api/changes/elt_destinations/:id/post.md)

---

[API](https://skmtc.dev/weld/apis/weld-rest-api.md) - [All operations](https://skmtc.dev/weld/apis/weld-rest-api/llms.txt) - [OpenAPI document](https://skmtc.dev/weld/apis/weld-rest-api/revisions/0e768a2ead18?raw)