Change requests are part of the same early access as maintenance programs. Reach out to your Slite contact to have them turned on for your workspace.
Overview
Your own scripts or external tools can create change requests, so suggested updates still go through human review.
MCP usage
Use the MCP tools to interact with change requests programmatically:
request-change: Create a new change request from a command. It takes the same fields as the API endpoint below.
read-change-request: Retrieve the status and URL of an existing change request. It takes the change request id.
API endpoint
Create a change request
POST https://api.slite.com/v1/change-requests
Authenticate with an API key, passed either as Authorization: Bearer <API key> or as an x-slite-api-key header. To get an API key, see the Slite API Help Center article.
Request fields:
command (required): What to change, in plain words, or the exact content to write, in markdown or sliteml. The Agent reproduces exact content verbatim. Up to 50,000 characters.
editableNoteIds (required): The docs the request may change or add sub-docs under. Provide 1 to 20 ids. You must be able to edit each one.
sourceRoots (optional): Where the Agent may search for evidence. Up to 20 entries, each { "kind": "note" | "root" | "sourceType", "value": "<id or type>" }. note is a doc and its sub-docs, root is a connected source root, and sourceType is a whole connected source type such as GitHub. Without sourceRoots, the Agent doesn't search and works only from the command and the editable docs.
audienceUserIds (optional): Who reviews the request besides you. Up to 20 user ids. Each must be able to read every editable doc and doc root.
assigneeUserId (optional): Who the request is assigned to: you (the default), or a member of the audience who can edit every editable doc. Required when the key belongs to an account that can't review change requests, such as a service account.
title (optional): The request's title until the Agent names it. Up to 120 characters.
Request example:
{
"editableNoteIds":["<DOC_ID>"],
"command":"Change the office location to Berlin.",
Hand the url to the reviewers. Nothing changes in the docs until someone approves the request in Slite.
Read a change request
GET https://api.slite.com/v1/change-requests/{changeRequestId}
While the Agent is working, this endpoint returns 202 with a Retry-After header and a retryAfterSeconds field. Otherwise it returns 200. The status field can be:
processing: The Agent is working.
pending_review: Changes are waiting for review.
completed: Every proposed change has been reviewed.
no_changes: The Agent found nothing to change.
failed: The request failed.
Error codes
401: Invalid API key.
402: The workspace has run out of AI credits.
403: Change requests aren’t enabled for the workspace (change-request/not-enabled), or the user has no Slite Agent access (change-request/no-super-access).
422: Invalid input.
429: Rate limit reached, or too many change requests are in progress.
Listing and editing change requests through the API isn't available yet. If you need it, contact support.