Skip to main content
PUT

Overview

Saves the parameters you always pass to a service, so future calls can leave them out. One row exists per scope, service and tool (or whole service); this request creates it or replaces its defaults in full. At execution time the defaults are merged under the call’s input. A parameter the call omits, or sends as null or an empty string, takes the default; any other explicit value wins. The execution response lists what was filled in under defaults_applied. Defaults are identifiers and settings, never credentials. A default is refused with 400 when its key matches secret, token, password, api_key, authorization, private_key or credential, or when its value starts like a known secret (sk_live_, sk_test_, rk_live_, rk_test_, whsec_, ghp_, gho_, github_pat_, xoxa-, xoxb-, xoxp-, an AKIA access key id, or a JWT). Store those with Store Credential instead. Auth: Required. API key (danube-api-key header) or JWT. Organization-wide defaults need the owner or admin role in that organization, or the response is 403.

Path Parameters

string
required
The service UUID or slug. Unknown services return 404.

Body Parameters

object
required
Parameter name to value. Must be a JSON object; every key must be a non-empty string.
string
Scope the row to one tool. Omit for a service-wide row.
string
default:"user"
user for your own defaults, org for organization-wide defaults. Anything else is 400.
string
Required when scope is org

Response

The stored row.
string
Row UUID
string
Your profile id for a user row, else null
string
The organization id for an org row, else null
string
The service UUID
string
The tool UUID, or null for a service-wide row
object
The saved defaults
string
When the row was created
string
When the row was last replaced

Example

The Python and TypeScript SDKs do not wrap this endpoint yet.

MCP Tool

This endpoint is also available as the set_parameter_defaults MCP tool, which always writes user scope: