---
title: "Run JavaScript in a running profile's page; 64 KiB result cap, 10 s timeout."
method: POST
path: "/v1/profiles/{id}/evaluate"
---

# Run JavaScript in a running profile's page; 64 KiB result cap, 10 s timeout.

`POST /v1/profiles/{id}/evaluate`

## Request

- Base URL: `http://127.0.0.1:10108`
- URL: `http://127.0.0.1:10108/v1/profiles/{id}/evaluate`
- Auth: HTTP bearer

Runs the JavaScript expression inside the running profile's page, with the page's own access to its cookies, storage and logged-in session. It can change or submit anything the page can. The result is cut at 64 KiB; the call gives up after 10 s.

## Path parameters

- `id` string, required

## Request body

- object
  - `dialog` 'dismiss' | 'accept'
  - `expression` string, required
  - `prompt_text` string

## Response `200`

The expression's value as text, cut at 64 KiB, with any JS dialog it opened.

- object
  - `dialogs` object[]
    - `accepted` boolean, required
    - `kind` 'alert' | 'confirm' | 'prompt' | 'beforeunload', required
    - `message` string, required
  - `text` string, required
  - `truncated` boolean, required

## Other responses

- `400`: The id is not a uuid, or the body is missing a field or has a value out of range.
- `401`: No bearer token, or not a token this app issued. The body is empty: it never says which.
- `403`: Refused by the plan: it no longer includes the local API (checked on every request), or it does not allow this action (profile or schedule limit, parallel runs). A request whose Host header is not loopback is also 403, with an empty body.
- `409`: The profile is not running, its tab is gone, or the page did not answer in time.
- `500`: Veilus failed: storage could not be read or written, or a task panicked. The message says what failed; retrying rarely helps.

---

[API](https://skmtc.dev/veilus/apis/veilus-local-api.md) · [All operations](https://skmtc.dev/veilus/apis/veilus-local-api/llms.txt) · [OpenAPI document](https://skmtc.dev/veilus/apis/veilus-local-api/revisions/67ac3818f9d2?raw)