CreateConnectionLinkInput
The request body for generating a connection link. The link lets a third party work on a single connection without any access to the tenant, in one of two modes: * **Create** a new connection - provide either a ``source_name`` (call the ``get_connection_source_names`` endpoint to list them) or an explicit ``connection_type``, exactly as when creating a connection. * **Edit an existing** connection - provide its ``connection_id``. The link then opens that connection with its current values filled in, and the type is taken from the connection itself.
Properties
| Name | Type | Description |
|---|---|---|
| connection_id | object | Optional. The id of an existing connection to share for editing. When provided the link opens that connection with its current values filled in, and neither 'source_name' nor 'connection_type' is need |
| source_name | object | Optional. The source_name of the data source or target the link creates a connection for; the connection type is resolved from it. Provide this or 'connection_type'. Do not guess this value: call the |
| segment | object | Optional. Disambiguates a source_name that is available as both a source and a target (e.g. 'snowflake'). One of 'source' or 'target'. |
| connection_type | object | Optional. The connection type. When omitted it is resolved from 'source_name'. When provided it is validated to exist and takes precedence. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/rivery/json-schema/rivery-create-connection-link-input-schema.json",
"title": "CreateConnectionLinkInput",
"description": "The request body for generating a connection link.\n\nThe link lets a third party work on a single connection without any access to the tenant, in\none of two modes:\n\n* **Create** a new connection - provide either a ``source_name`` (call the\n ``get_connection_source_names`` endpoint to list them) or an explicit ``connection_type``,\n exactly as when creating a connection.\n* **Edit an existing** connection - provide its ``connection_id``. The link then opens that\n connection with its current values filled in, and the type is taken from the connection\n itself.",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/rivery-connections-api-openapi.yml#/components/schemas/CreateConnectionLinkInput",
"properties": {
"connection_id": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Connection Id",
"description": "Optional. The id of an existing connection to share for editing. When provided the link opens that connection with its current values filled in, and neither 'source_name' nor 'connection_type' is needed. The link can only be used on this connection - it cannot create or edit any other one."
},
"source_name": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Source Name",
"description": "Optional. The source_name of the data source or target the link creates a connection 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 a returned source_name verbatim."
},
"segment": {
"anyOf": [
{
"$ref": "#/$defs/ConnectionSegmentEnum"
},
{
"type": "null"
}
],
"description": "Optional. Disambiguates a source_name that is available as both a source and a target (e.g. 'snowflake'). One of 'source' or 'target'."
},
"connection_type": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Connection Type",
"description": "Optional. The connection type. When omitted it is resolved from 'source_name'. When provided it is validated to exist and takes precedence."
}
},
"type": "object",
"$defs": {
"ConnectionSegmentEnum": {
"type": "string",
"enum": [
"source",
"target"
],
"title": "ConnectionSegmentEnum",
"description": "The segment a connection is created for, used to disambiguate a source_name that is\navailable as both a source and a target (e.g. \"snowflake\")."
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/json-schemas/rivery-create-connection-link-input"
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.