Create a command type
const url = 'https://example.com/api/v1/command-types';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"description":"example","display_name":"example","name":"example","params_schema":"example","settle_window_seconds":1,"target_property_type":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/api/v1/command-types \ --header 'Content-Type: application/json' \ --data '{ "description": "example", "display_name": "example", "name": "example", "params_schema": "example", "settle_window_seconds": 1, "target_property_type": "example" }'Registers a custom command type (official=false). The name must be a valid key; a target property, when set, must be registered. Gated by command_type:create.
Request Body required
Section titled “Request Body required ”object
A URL to the JSON Schema for this object.
What the command does
A human label
The command type name (lowercase, dot-hierarchied)
A JSON Schema fragment for the params
The actuation window in seconds (0 = fire-and-forget)
The property this command sets, for settlement
Responses
Section titled “ Responses ”Created
object
A URL to the JSON Schema for this object.
The command type’s uuid, the stable form of name
A JSON Schema fragment for the invocation params
How long the device is given to actuate before a mismatch is a failed command
The property this command sets (empty for a fire-and-forget command)
Example
{ "$schema": "/api/v1/schemas/CommandTypeBody.json"}default
Section titled “default ”Error
object
A URL to the JSON Schema for this object.
A human-readable explanation specific to this occurrence of the problem.
Optional list of individual error details
object
Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’
Error message text
The value at the given location
A URI reference that identifies the specific occurrence of the problem.
HTTP status code
A short, human-readable summary of the problem type. This value should not change between occurrences of the error.
A URI reference to human-readable documentation for the error.
Example
{ "$schema": "/api/v1/schemas/ErrorModel.json", "detail": "Property foo is required but is missing.", "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "about:blank"}