DEdeepnote
Projects
Files

Publish a static site

Changed on

Replaces a bounded set of files beneath _deepnote_static/, optionally prunes stale static files, then enables static sharing and applies an explicit viewer API-access setting. All content is validated before storage changes. A storage failure can leave a partial publish; retry the same file set to converge. Concurrent publishes are unsupported and use last-write-wins behavior. Use the Deepnote CLI for sites above the documented file or byte limits.

post/projects/{projectId}/static-files/publish

Request

  • Base URL
    https://api.deepnote.com/v2
  • URL
    https://api.deepnote.com/v2/projects/{projectId}/static-files/publish
  • Auth
    HTTP bearer

Path parameters

projectIdstring uuid required

Project whose static site will be replaced.

Request body

pruneboolean

Remove files beneath _deepnote_static/ that are not included in this publish.

apiAccess'enabled' | 'disabled'

Explicitly enable or disable viewer API access. Omit to preserve the current setting.

Example request

{
  "files": [
    {
      "path": "assets/app.js"
    }
  ]
}

Response

Static site published

projectIdstring uuid required
urlstring uri required
uploadedinteger required
prunedinteger required
sharingEnabledtrue required
apiAccessEnabledboolean required

Changes