Documentation Index

Fetch the complete documentation index at: https://developer.rocket.chat/llms.txt

Use this file to discover all available pages before exploring further.

Update Fingerprint

Prev Next
Post
/api/v1/fingerprint

Confirms how the workspace deployment should be handled after Rocket.Chat detects a change to its deployment fingerprint.

On startup, Rocket.Chat generates a deployment fingerprint based on the configured Site_Url and MongoDB connection string. If the generated fingerprint differs from the stored value, Rocket.Chat assumes the workspace may have been duplicated, migrated, or reconfigured.

Use this endpoint to confirm how the deployment should be treated:

  • new-workspace: Treats the deployment as a new workspace. This clears the existing Rocket.Chat Cloud registration data and related credentials so the workspace can register again as a new instance. Use this option for cloned environments, staging instances created from production backups, or other duplicated deployments.

  • updated-configuration: Confirms that the deployment is the same workspace and that only its configuration has changed. This preserves the existing Rocket.Chat Cloud registration and is intended for legitimate migrations, infrastructure changes, or Site_Url updates.

After processing either option, Rocket.Chat marks the deployment fingerprint as verified and dismisses the fingerprint verification prompt.

Permission required: manage-cloud

Changelog

Version Description
8.6.0 Added an authorization check. Callers without the manage-cloud permission now receive a 403 error instead of a successful response.
Header parameters
X-Auth-Token
stringRequired

The authToken of the authenticated user.

ExampleRScctEHSmLGZGywfIhWyRpyofhKOiMoUIpimhvheU3f
X-User-Id
stringRequired

The userId of the authenticated user.

ExamplerbAXPnMktTFbNpwtJ
Body parameters
Example
{
  "setDeploymentAs": "new-workspace"
}
object
setDeploymentAs
string Required

Specifies how Rocket.Chat should handle a detected deployment fingerprint change. Use new-workspace to reset the current workspace registration and register the deployment as a new workspace, or updated-configuration to preserve the existing workspace registration and confirm that only the deployment configuration has changed. Either new-workspace or updated-configuration.

Examplenew-workspace
Responses
200

OK

Success
{
  "success": true
}
object
success
boolean
400

Bad Request

Invalid Parameter
{
  "success": false,
  "error": "Invalid body params",
  "errorType": "error-invalid-body-params"
}
object
success
boolean
error
string
errorType
string
401

Unauthorized

Authorization Error
{
  "status": "error",
  "message": "You must be logged in to do this."
}
object
status
string
message
string
403

Forbidden

Permission Error
{
  "success": false,
  "error": "User does not have the permissions required for this action [error-unauthorized]",
  "errorType": "error-unauthorized"
}
object
success
boolean
error
string
errorType
string