Provision or re-provision daemon
Changed onCreates 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.
Request
- Base URLhttps://app.scanopy.net
- URLhttps://app.scanopy.net/api/v1/daemons/provision
- Auth
- API key in header Authorization
- or API key in cookie session_id
Request body
Response
Daemon provisioned successfully
Example response
{
"data": {
"daemon": {
"url": "https://daemon.example.com:60073",
"version": "0.17.7"
}
},
"meta": {
"api_version": 1,
"server_version": "0.19.4"
}
}Changes
- info
added the required property
///to the response with the status
- info
- breaking
removed
subschema #2: Networkfrom the/request propertyoneOflist - breaking
removed the required property
//////from the response with the status - warning
removed the request property
- info
added the new optional request property
- info
added
subschema #2: Siteto the/request propertyoneOflist - info
added the required property
//////to the response with the status
- breaking