ScanopyScanopy
Daemons

Email install command to current user

Session-only, and IsUser says so at the extractor rather than in the body. "The current user" has no answer for an automation identity: a user API key carries user_id but no address, so this endpoint could never serve one. An API key that wants the command reads it directly from GET /api/v1/daemons/{id}/install-command.

POST
/api/v1/daemons/email-install-command

Authorization

session
session_id<token>

Browser session cookie. Obtained via /api/auth/login.

In: cookie

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Request body for emailing an install command to the authenticated user.

Response Body

application/json

application/json

application/json

curl -X POST "https://example.com/api/v1/daemons/email-install-command" \  -H "Content-Type: application/json" \  -d '{    "install_command": "string",    "os": "linux"  }'
{
  "meta": {
    "api_version": 1,
    "server_version": "0.17.13"
  },
  "success": true,
  "data": null,
  "error": "string"
}
{
  "meta": {
    "api_version": 1,
    "server_version": "0.17.13"
  },
  "success": true,
  "code": "string",
  "error": "string",
  "params": {
    "property1": null,
    "property2": null
  }
}
{
  "meta": {
    "api_version": 1,
    "server_version": "0.17.13"
  },
  "success": true,
  "code": "string",
  "error": "string",
  "params": {
    "property1": null,
    "property2": null
  }
}

Bulk delete daemons

Previous Page

Provision a daemon, or re-provision an existing one

Creates a daemon record on the server before the daemon is installed and mints an API key bound to it 1:1. Returns the daemon record and that key, which is shown only once and must be configured on the daemon. When `daemon_id` is supplied the existing record is reused instead of creating a new one, giving a legacy daemon (one with no bound key) a pathway to a dedicated key without losing its host, discovery jobs, or history. Re-provisioning always mints a fresh key. Install commands are not built here — fetch them from the install-command endpoint, which builds them idempotently and fills in the key this returns. That keeps a display-only regenerate (an OS switch, an advanced-setting change) from re-minting the key.