secrets

Set which credentials one need uses for your instance of a trigger (cron job, subscription, or webhook), but only to ...

Set which credentials one need uses for your instance of a trigger (cron job, subscription, or webhook), but only to a value you already proposed with credentialMappingPropose and the person approved from that link, for example to switch back after the pick changed. The pick is resolved and written the same way Approve writes it. Anything else is refused: propose it instead. Never turns a trigger on; a trigger that is off needs approval. Needs package:execute on the package and an agent credential (MCP OAuth client, CLI, or API token); the person's own approval page and Credentials tab do not use this.

Org permission: none (touches no org data).

put/v1/credential-trigger-picks

Request

  • Base URL: https://api.kody.codes
  • URL: https://api.kody.codes/v1/credential-trigger-picks
  • Auth: HTTP bearer

Request body

packageIdstring

Saved-package UUID. Use when the scoped name is not known, or for a stable ref.

kodyIdstring

Package name (@owner/leaf or the name leaf). Prefer this when you know the name.

needKeystring required

The credential need key.

Response

Success.

needKeystring required
messagestring required

Changes

No recorded changes to this operation across all 1 revision of this API.