List applied database migrations
Every change applied to this database, oldest first. Each carries restore_to — the state the database was in before that change ran — so any of them can be undone with db/restore without anyone having captured a restore point in advance.
Authorizations
API key in the format: Bearer {api_token}
Path Parameters
The resource ID (e.g., "prod_abc123") or slug (e.g., "my-product")
Query Parameters
Which database to use. A site normally has exactly one, production, and that is the default — the live database the site reads. development is only valid if a separate development database has been provisioned for this site; asking for one that doesn't exist is an error rather than a silent fall back to production. The response echoes the environment that was used.
development, production 
