Update Workspace

curl --request PUT \
  --url https://api.usedatabrain.com/api/v2/workspace \
  --header 'Authorization: Bearer dbn_live_abc123...' \
  --header 'Content-Type: application/json' \
  --data '{
    "name": "Sales Analytics",
    "connectionType": "DATASOURCE",
    "datasourceName": "postgres-production"
  }'

{
  "data": {
    "name": "Sales Analytics"
  },
  "error": null
}

curl --request PUT \
  --url https://api.usedatabrain.com/api/v2/workspace \
  --header 'Authorization: Bearer dbn_live_abc123...' \
  --header 'Content-Type: application/json' \
  --data '{
    "name": "Sales Analytics",
    "connectionType": "DATASOURCE",
    "datasourceName": "postgres-production"
  }'

{
  "data": {
    "name": "Sales Analytics"
  },
  "error": null
}

curl --request PUT \
  --url https://api.usedatabrain.com/api/v2/workspace \
  --header 'Authorization: Bearer dbn_live_abc123...' \
  --header 'Content-Type: application/json' \
  --data '{
    "name": "Sales Analytics",
    "connectionType": "DATASOURCE",
    "datasourceName": "postgres-production"
  }'

{
  "data": {
    "name": "Sales Analytics"
  },
  "error": null
}

PUT

https://api.usedatabrain.com

api

workspace

curl --request PUT \
  --url https://api.usedatabrain.com/api/v2/workspace \
  --header 'Authorization: Bearer dbn_live_abc123...' \
  --header 'Content-Type: application/json' \
  --data '{
    "name": "Sales Analytics",
    "connectionType": "DATASOURCE",
    "datasourceName": "postgres-production"
  }'

{
  "data": {
    "name": "Sales Analytics"
  },
  "error": null
}

Update the connection settings of an existing workspace. You can switch between datasource, datamart, or multi-datasource configurations. Updating a workspace also updates all associated metrics to use the new connection.

Important: Updating a workspace connection will automatically update all metrics in that workspace to use the new datasource or datamart connection. Ensure the new connection has compatible table and column structures to avoid breaking existing metrics.

The workspace name is used to identify which workspace to update and cannot be changed through this endpoint. To rename a workspace, you’ll need to create a new one and migrate your content.

Authentication

All API requests must include your API key in the Authorization header. Get your API token when creating a data app - see our data app creation guide for details. Finding your API token: For detailed instructions, see the API Token guide.

Headers

Authorization

string

required

Bearer token for API authentication. Use your API key from the data app.

Authorization: Bearer dbn_live_abc123...

Content-Type

string

required

Must be set to application/json for all requests.

Content-Type: application/json

Request Body

name

string

required

Name of the existing workspace to update. Must match exactly (case-sensitive).

Show Finding workspace names

Use the List Workspaces API to get all workspace names
Names are case-sensitive and must match exactly
This field identifies which workspace to update

connectionType

string

required

New connection type for the workspace. Must be one of: DATASOURCE, DATAMART, or MULTI_DATASOURCE.

Show Connection type details

DATASOURCE: Connect directly to a single datasource
DATAMART: Connect to a pre-configured datamart
MULTI_DATASOURCE: Allow connections to multiple datasources within this workspace

Note: Changing connection type will update all metrics in this workspace.

datasourceName

string

Name of the datasource to connect to this workspace.Required when connectionType is DATASOURCE.

Show Datasource considerations

Must be an existing datasource in your organization
Use the exact name as stored in datasource credentials
Names are case-sensitive
All metrics will be updated to use this datasource

datamartName

string

Name of the datamart to connect to this workspace.Required when connectionType is DATAMART.

Show Datamart considerations

Must be an existing datamart in your organization
Use the List Datamarts API to find available datamarts
Names are case-sensitive
All metrics will be updated to use this datamart’s datasource

Response

data

object

Contains the updated workspace information on success.

Show data properties

name

string

The name of the successfully updated workspace.

error

null | object

Error object if the request failed, otherwise null for successful requests.

Show error properties

code

string

Error code identifying the type of error.

message

string

Human-readable error message describing what went wrong.

Examples

HTTP Status Code Summary

Status Code	Description
`200`	OK - Workspace updated successfully
`400`	Bad Request - Invalid request parameters
`401`	Unauthorized - Invalid or missing API key
`500`	Internal Server Error - Server error occurred

Possible Errors

Error Code	HTTP Status	Description
`INVALID_REQUEST_BODY`	400	Missing or invalid parameters
`WORKSPACE_DOES_NOT_EXIST`	400	Workspace not found
`INVALID_DATASOURCE_NAME`	400	Datasource not found
`INVALID_DATAMART_NAME`	400	Datamart not found
`INVALID_DATA_APP_API_KEY`	401	Invalid API key
`INTERNAL_SERVER_ERROR`	500	Server error

List Workspaces

Embed Data App API (CRUD)

⌘I

Authentication

Datasource APIs

Datamart APIs

Workspace APIs

Embeds

Embedding APIs (Legacy)

Data App APIs

Metric APIs

Authentication

Headers

Request Body

Response

Examples

HTTP Status Code Summary

Possible Errors

Authentication

Datasource APIs

Datamart APIs

Workspace APIs

Embeds

Embedding APIs (Legacy)

Data App APIs

Metric APIs

​Authentication

​Headers

​Request Body

​Response

​Examples

​HTTP Status Code Summary

​Possible Errors

Authentication

Headers

Request Body

Response

Examples

HTTP Status Code Summary

Possible Errors