---
title: "Add Connection"
method: POST
path: "/v1/accounts/{account_id}/environments/{environment_id}/connections"
tags: ["Connections"]
---

# Add Connection

`POST /v1/accounts/{account_id}/environments/{environment_id}/connections`

## Request

- Base URL: `https://api.rivery.io`
- URL: `https://api.rivery.io/v1/accounts/{account_id}/environments/{environment_id}/connections`
- Auth: HTTP bearer

**Authorization scope:** `connection:edit` 
 
 **Creates a new connection entity.**
****
**The connection type is resolved from the required ``source_name`` (the name of a data source**
**or target). A ``connection_type`` may still be provided explicitly, in which case it is**
**validated and takes precedence. An optional ``segment`` disambiguates a ``source_name``**
**available as both a source and a target (e.g. "snowflake").**

## Path parameters

- `account_id` string, required
- `environment_id` string, required

## Request body

- AddConnectionInput: The request body for creating a connection. Provide either a ``source_name`` (the name of a data source or target - call the ``get_connection_source_names`` endpoint to list them) or an explicit ``connection_type``; the connection type is resolved from whichever is given. The connection-type-specific properties (host, password, warehouse, etc.) are passed as extra top-level fields. To discover exactly which properties a connection type needs, call the ``get_connection_type`` endpoint (GET /connections_types/{connection_type}).
  - `source_name` string, nullable: Optional. The source_name of the data source or target the connection is created for; the connection type is resolved from it. Provide this or 'connection_type'. Do not guess this value: call the 'get_connection_source_names' endpoint first and use one of the returned source_names verbatim.
  - `connection_name` string, required: The name of the connection
  - `segment` 'source' | 'target', nullable: The segment a connection is created for, used to disambiguate a source_name that is available as both a source and a target (e.g. "snowflake").
  - `connection_type` string, nullable: Optional. The connection type. When omitted it is resolved from 'source_name'. When provided it is validated to exist and takes precedence. Do not guess this value: resolve it from 'source_name' by calling 'get_connection_source_names' and using the 'connection_type' on the matching entry.

## Response `201`

Successful Response

- object

## Other responses

- `422`: Validation Error

## Changes

- **2026-11-09** `75e8c5d8f575`: 1 info
  - api tag `MCP` removed
- **2026-10-24** `00b90942c8d6`: 1 info
  - endpoint added
- **2026-10-24** `0a8241f415c4`: 1 breaking
  - api path removed without deprecation
- **2026-08-06** `ddd6b1c27983`: 1 breaking, 6 info
  - added the new required request property `connection_name`
  - api tag `Connections` added
  - api tag `MCP` added
  - api tag `Beta Endpoints` removed
  - …3 more

[Operation history](https://skmtc.dev/rivery/apis/boomi-data-integration-api/changes/v1/accounts/:account_id/environments/:environment_id/connections/post.md)

---

[API](https://skmtc.dev/rivery/apis/boomi-data-integration-api.md) - [All operations](https://skmtc.dev/rivery/apis/boomi-data-integration-api/llms.txt) - [OpenAPI document](https://skmtc.dev/rivery/apis/boomi-data-integration-api/revisions/f62df1a59d33?raw)
