change_ack
Acknowledge delivered events and advance the contiguous consumer checkpoint.
When to use it
Use change_ack to acknowledge changes. On the workspace endpoint, pass projectId from project_list. On a project-scoped endpoint, the project is already bound: omit that argument and use the schema discovered from that endpoint.
Arguments
| Name | Type | Required | Default | Constraints |
|---|---|---|---|---|
consumer | string | Yes | — | Minimum length: 1; Maximum length: 100 |
eventIds | array | Yes | — | Minimum items: 1; Maximum items: 100; Items: string |
projectId | string | Yes | — | Format: uuid; Pattern constraint; see full schema |
View the complete input schema, including nested contracts and alternative shapes. The schema is extracted from the workspace server’s Zod definitions. Runtime validation also enforces custom checks that JSON Schema cannot express.
Response shape
The operation-specific payload is returned in data; its contents follow the operation described above.
MCP returns a text block containing the JSON operation result and a
structuredContent copy. The envelope includes data, completeness,
truncated, freshness, and warnings. Depending on the operation it can also
include nextCursor, evidence, job, or receipt.
Check those fields before treating a conversational summary as the result.
When a job is returned, inspect its status with the appropriate execution tool;
a queued response is not confirmation that work finished. Follow evidence links
when checking the underlying records.
Input methods
This request illustrates the argument structure. Replace every angle-bracket placeholder with a real value and supply any applicable optional fields from the schema. Nested business contracts must match your actual configuration. Send it through an authenticated, initialized MCP client; this JSON alone does not establish a session or sign you in.
Use Semogram’s change_ack tool to acknowledge changes. Inspect the required inputs and target first, then show me what will change before executing it.
Choose the project explicitly before making this request. Use real resource IDs returned by earlier reads; a resource name is not a UUID. Do not fill missing business inputs with invented values.
Use a workspace API key with data:read. Set SEMOGRAM_API_KEY in your shell; replace resource placeholders with real IDs. This is an HTTP resource request, not an MCP JSON-RPC message.
curl --request POST "https://platform.semogram.com/api/v1/projects/<PROJECT_ID_UUID>/changes/ack" \
--header "Authorization: Bearer ${SEMOGRAM_API_KEY}" \
--header "Content-Type: application/json" \
--data-binary @- <<'JSON'
{
"consumer": "<CONSUMER>",
"eventIds": [
"<EVENT_IDS_UUID>"
]
}
JSONThis is an MCP tools/call request, not a form to paste into Semogram. Send it through an authenticated, initialized MCP client.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "change_ack",
"arguments": {
"consumer": "<CONSUMER>",
"eventIds": [
"<EVENT_IDS_UUID>"
],
"projectId": "<PROJECT_ID_UUID>"
}
}
}FAQ
What access and approvals are required?
Required permission scopes: data:read.
OAuth uses current workspace membership; API keys use their assigned scopes
and grants. Discovery can exclude tools the caller cannot use.
Read-only annotation: No. Destructive annotation: No. Follow the operation’s declared contract and any applicable server-side approval policy.
How should I handle retries?
Do not assume repeated calls are safe merely because the client offers Retry. Inspect the result or existing request before repeating work that changes state. For 429 responses, honor Retry-After rather than retrying immediately.
Why is this tool missing or returning an error?
Confirm the workspace, resource IDs, and permission scopes. Read the returned error before changing the request. See connection, authentication and troubleshooting for sign-in, scope, resource access, and rate-limit errors.