Get the Build Cache
Read an application's build cache: the packages its production builds downloaded (npm, pnpm or Yarn), kept so the next build doesn't download them again. Branch and pull request previews use it but never change it. See Build cache for how it works.
It needs read access to applications. An app whose builds don't use the cache (a managed backend, a function, a WordPress site) answers exists: false.
Path parameters
Response (200 OK)
true when the app has a build cache. false when no production build has saved one yet, or since it was cleared, started fresh or deleted.static: the build of a static site or of a full-stack app's front end.0 when there is none.null when there is none.npm, pnpm or yarn. "" when there is none.Errors
application not foundClear the Build Cache
Clear an application's build cache. The next production build downloads every package again and saves a new cache, so it takes longer. A build that had already started keeps the cache it started with. The live version doesn't change.
It needs a role that can change applications. Clearing an app that has no cache also answers 204, so you can repeat it safely. It works while the app is paused.
Path parameters
Response (204 No Content)
No body.
Errors
application not found