Use the playground below to explore public asset-library reads through a story-first setup flow.

Start from a folder, media-search, or share-token story in the setup rail. Restore safe route context locally, confirm the selected operation in Scalar, and use explicit share links when you need to preserve a non-secret request draft alongside the route context.

The playground loads the OpenAPI spec from /swagger/dam-api.json and stays in sync with the reference pages.

What the playground restores and shares

• The setup rail restores the selected public-read story, operation, server, and route variables from safe local state.
• Compact URL sync stays conservative and is limited to the selected story plus safe route context.
• Explicit share links can also include the optional request-draft field for non-secret JSON context, but that field never auto-syncs into the URL or local storage.
• Bearer auth remains session-only for the current browser tab and is never copied into shared links.
• The request-draft field is review context only. It does not rewrite the Scalar request editor or change the OpenAPI contract.
• Exact endpoint methods, parameters, schemas, and delivery contracts are defined by the OpenAPI reference.

Related

• Asset library reads and DAM administration - public reads and Management administration boundaries
• Folders reference - public folder reads
• DAM reference - Management administration pages
• OpenAPI spec - raw spec file