Skip to content
Plune Plune Plune Docs

Is the run’s public report on

GET
/v1/runs/{id}/public-report
 
curl --request GET \
  --url https://beta-api.plune.ai/v1/runs/example/public-report \
  --header 'Authorization: Bearer <token>'

The state of the run’s public report (#1263): { enabled: false }, or { enabled: true, createdAt, createdBy, expiresAt, expired, passwordProtected }. Never the token, the password or its hash, or any piece of it: the server keeps only a hash of it, and the link is shown once, in the answer to PUT that made it. Every member of the project reads this, a reader too.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
id
required
string

Responses

Section titled “ Responses ”

200

Section titled “200 ”

The state

Media type application/json
object
enabled
required
boolean
createdAt

When the link was made. Only when enabled.

string format: date-time
createdBy

The id of the person who made it. Only when enabled.

string
expiresAt

When the link stops answering (#1264). Only when enabled.

string format: date-time
expired

expiresAt has passed: the address answers 410, and PUT makes a new link. Only when enabled.

boolean
lockedUntil

Set while too many wrong passwords have locked the address (10 in 15 minutes): until when. Null otherwise. Per API instance. Only when enabled.

string | null format: date-time
passwordProtected

A password is set (the server keeps only a salted hash of it). Only when enabled.

boolean
Example generated
{
  "enabled": true,
  "createdAt": "2026-04-15T12:00:00Z",
  "createdBy": "example",
  "expiresAt": "2026-04-15T12:00:00Z",
  "expired": true,
  "lockedUntil": "2026-04-15T12:00:00Z",
  "passwordProtected": true
}

401

Section titled “401 ”

No / invalid token or session

404

Section titled “404 ”

No such run in your projects

Media type application/json
object
error
required
string
Example generated
{
  "error": "example"
}