dots.v2.agents.configs.post()
Generated on 5 Nov 2026
from DoTs version
v1.23.0
Usage
client.v2.agents.configs.post(body: Agent_config_create_request, requestConfiguration?: RequestConfiguration<object>): Promise<undefined | Agent_config_response>Description
Accepts name, environment-spec YAML text, and optional Insights telemetry opt-in. Tenant secrets are declared inside the environment spec (write-only values), not as sibling request fields. Responses never echo secret values; GET/create may include credential slot metadata (name/source/provider only). Configs are immutable after create.
Parameters
namestring requiredExample:
support-agentConfig name, case-insensitively unique among the team's active configs.
manifestYamlstring requiredExample:
apiVersion: agents.digitalocean.com/v1alpha1 kind: Agent spec: runtime: adapter: opencodeCustomer environment-spec YAML text. The HTTP JSON body is capped at 1 MiB and this field is capped at 512 KiB.
insightsobject optionalPer-signal DigitalOcean Insights telemetry opt-in, mirroring the Insights-owned schema insights.telemetry.opt_in. Each signal is independently optional and tri-state: omitted or null records that the customer expressed no choice and falls back to the product default, which is NOT equivalent to false.
Show child properties
metricsboolean or null optionalAccepted and stored for parity with the Insights schema, but metrics are always collected: unregistered metrics are dropped at ingest rather than opted out of here.
logsboolean or null optionalWhether the agent's logs are sent to Insights.
tracesboolean or null optionalWhether the agent's traces are sent to Insights.
Request Sample
Response Example
More Information
See /v2/agents/configs in the API reference for additional detail on responses, headers, parameters, and more.