Performs find/replace operations on content using the specified model.
This endpoint allows you to replace views or fields across all documents associated with the model. This is useful when renaming model elements and need to update all references.
Can be either an Organization API Key or Personal Access Token (PAT).
Include in the Authorization header as: Bearer YOUR_TOKEN
The ID of the model to perform find/replace against.
The user ID to act on behalf of. Only valid when using an organization API key.
User-scoped API keys cannot use this parameter and will receive a 403 error if provided.
The value to find. Used with find_or_replace_type to scope the search:
VIEW - The name of the view to findFIELD - The fully qualified name of the field to find, specified as view_name.field_nameTOPIC - The name of the topic to findThe replacement value.
VIEW - The name of the replacement viewFIELD - The fully qualified name of the replacement field, specified as view_name.field_nameTOPIC - The name of the replacement topicThe type of find/replace operation.
VIEW - Replace view referencesFIELD - Replace field references. find and replacement values must be the fully qualified name of the field, e.g. view_name.field_name.TOPIC - Replace topic referencesVIEW, FIELD, TOPIC The branch ID to perform the operation on. If not provided, operates on the main model.
When enabled, include personal folders.
When provided, scopes the find/replace action to the specified workbook.
Must be the workbook model's internal UUID — visible in the model IDE URL as /model/{uuid}. This is not the same as the document's URL identifier (slug) that appears in the dashboard or workbook URL (for example, /dashboards/abc123). Passing a document identifier / slug will silently return 0 replacements instead of raising an error.
"550e8400-e29b-41d4-a716-446655440000"
Find/replace operation completed successfully
The number of queries that had replacements made.
The number of documents that had replacements made.
The number of workbook models that had replacements made.
The number of dashboard filters that had replacements made.
The number of documents skipped because they require a pull request to publish.