What a schema change would break
List permission rules, saved views, pages, and other fields that read the fields or tables you propose to remove.
POST/v1/apps/{appId}/schema/impact
Returns the same list that causes fields.delete and tables.delete to be refused until you send acknowledge=true. Matches pages by the names in their last build; references use IDs, so renaming breaks nothing and returns no results. Advisory only; changes nothing.
Requires the schema:read scope. Operation schema.impact. MCP tool schema_impact. CLI: grid82 schema impact (npx grid82).
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
appId | string | yes |
Headers
| Name | Type | Required | Description |
|---|---|---|---|
Idempotency-Key | string | no | Any unique string. Sending the same key with the same request again returns the first response (marked Idempotency-Replayed: true) instead of running it twice. Reusing it for a different request is refused with 409. Kept for 24 hours. Up to 255 characters. |
Request body
| Field | Type | Required | Description |
|---|---|---|---|
drops | object[] | no | Default []. |
renames | object[] | no | Default []. |
Response
Success
dataobjectrequiredRefused
errorobjectrequired