---
deprecated: true
search:
  tags:
    - Multitenancy Recipe
    - PUT
seo:
  description: >-
    This API is deprecated. Please use the v2 version of… Reference for the PUT
    /recipe/multitenancy/connectionuridomain endpoint in the Core Driver
    Interface API.
sidebar:
  badge: PUT
  label: Upsert connection URI domain
title: Upsert connection URI domain
type: openapi-operation
---
This API is deprecated. Please use the v2 version of this API. In the v2 version of the API, the login methods are no longer enabled using the `emailPasswordEnabled`, `thirdPartyEnabled` and `passwordlessEnabled` inputs. Instead, they are enabled using factorIds (such as emailpassword, otp-email, etc) specified in the `firstFactors` and `requiredSecondaryFactors` inputs. Please refer [Multitenancy Docs](https://supertokens.com/docs/multitenancy/new-tenant) to know the list of factorIds available.

Note: This deprecated API still accepts those `emailPasswordEnabled`, `thirdPartyEnabled` and `passwordlessEnabled` inputs for backward compatibility.

Create or update a connection uri domain.

SuperTokens subscription license key is required, if not using the base connection uri domain.

This request must originate from public app and public tenant on the base
connection uri domain.

If creating a new connection uri domain, only the login methods set to true will be enabled and rest will be disabled by default.

`firstFactors` and `requiredSecondaryFactors` can be set to null to remove all entries in the core, or a non empty string array to be updated in the core. Setting of empty array is disallowed.

Note: the create/update will fail if a login method is not enabled and a relavant factor is added to either `firstFactors` or `requiredSecondaryFactors`. For example, `emailPasswordEnabled` cannot be set to `false` if `emailpassword` is present in the `firstFactors` array.

If updating an existing connection uri domain,
1. core will keep the existing state of login methods and only update the ones that are specified in the request body.
2. Core config will be merged into existing config. To delete a key in the config, use a null value

Note: The core config must contain a unique connection to the storage layer, because sharing of database between 2 different connection uri domains is not allowed.

Note: Updation of core config is not allowed for the default connectionUriDomain. In order to update config for the default connectionUriDomain, you must edit the config.yaml or the docker env directly.

<Operation source="references-cdi" id="createorupdateconnectionuridomainput" />