Preview what deploying would change about the schema
The difference between the development database and the live one, described before it is applied — the statements, what they mean in plain language, and whether anything would be lost. Nothing runs. Show this to the user before deploying: a schema change that only becomes visible once it has happened is one nobody gets to object to.
Authorizations
API key in the format: Bearer {api_token}
Path Parameters
The resource ID (e.g., "prod_abc123") or slug (e.g., "my-product")
Response
Planned schema change
The live database already matches; deploying would change nothing.
What the change means, in language a non-technical merchant can act on.
The DDL that would run.
Anything that would be removed or rebuilt.

