save_profile_snapshot
Explicitly save the current monitored-watch category and native supplier-rank profile as an immutable 90-day baseline. Requires read and write access. No provider collection or schedule.
This command name is absent from deployment evidence dated 2026-09-20. Hosted availability for this current definition is unverified; inspect your connected catalog before invoking it. Verify the command and its input schema in the selected environment.
This operation changes saved state. Review its inputs and retry behavior before calling.
Example request
Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.Returned result
Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data instructuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.
Full response example
Full response example
Input fields
Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.Validation and omitted values
Requires watches:read and watches:write. Supply a new idempotencyKey for a new save. Reuse the same project and key after an uncertain response to retrieve the retained save, even if current source data has changed. An expired save requires a new key. Saves up to 1,000 non-archived enrolled watch rows with a 1,500,000-byte source and record bound. Active and paused monitors are included; one-off candidate checks are excluded. This is a watch-row population; it does not count unique physical links or distinct referring domains. Chosen categories, available current assessments and display categories remain separate. DataForSEO page and domain ranks retain their native 0-1000 scale and retrieval dates. Missing categories and scores remain unknown; repeated domain scores count once per watch. The immutable snapshot records a bounded read interval and expires after 90 days. A project can retain up to 500 unexpired snapshots. Project or workspace erasure removes the evidence; erasing a contained watch removes the entire snapshot. Saving starts no provider collection or recurring schedule.Output fields
Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.snapshot(object, required): additional fields rejectedreplayed(boolean, required): True when the response reuses an earlier request with the same idempotency value.
All fields and nested objects
All fields and nested objects
Errors and retries
When retrying with idempotencyKey, reuse the original value and the same arguments; preserve originally omitted optional fields. Generic HTTP puts idempotencyKey in the JSON body, while resource routes use the header where listed below. A changed payload under a reused key can conflict. Operation-specific errors includeINVALID_PROFILE_SNAPSHOT_INPUT, PROFILE_SNAPSHOT_ACCESS_DENIED, PROFILE_SNAPSHOT_SCHEMA_UNAVAILABLE, PROFILE_SNAPSHOT_LIMIT, PROFILE_SNAPSHOT_SOURCE_CHANGED, PROFILE_SNAPSHOT_EXPIRED.
See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.