Secret policies
Botyard REST API endpoints for secret policies.
10 endpoints in this group. Every request authenticates with an API key; see the API reference for the other groups.
- List Bot Secret Policies:
GET /v1/orgs/{org_id}/bots/{bot_slug}/secret-policies - Unassign Secret Policy:
DELETE /v1/orgs/{org_id}/bots/{bot_slug}/secret-policies/{policy_id} - Assign Secret Policy:
PUT /v1/orgs/{org_id}/bots/{bot_slug}/secret-policies/{policy_id} - List Secret Policies:
GET /v1/orgs/{org_id}/secret-policies - Create Secret Policy:
POST /v1/orgs/{org_id}/secret-policies - Get Secret Policy:
GET /v1/orgs/{org_id}/secret-policies/{policy_id} - Update Secret Policy:
PATCH /v1/orgs/{org_id}/secret-policies/{policy_id} - Delete Secret Policy:
DELETE /v1/orgs/{org_id}/secret-policies/{policy_id} - Get Secret Policy Bot Links:
GET /v1/orgs/{org_id}/secret-policies/{policy_id}/bot-links - Put Secret Policy Bot Links:
PUT /v1/orgs/{org_id}/secret-policies/{policy_id}/bot-links
List Schedule Command Runs
Command attempts for one schedule — outcome, exit code, attempt, log tail. Read-only. ``/runs`` answers "did the schedule fire?" from ``schedule_fires``; this answers "what did the command do?" from ``schedule_command_runs``, which lives in the platform database. A prompt schedule has no attempts, so it returns an empty page rather than an error. The schedule is resolved under this org+bot first, so another tenant's id 404s; the query itself is also scoped by org and bot.
List Bot Secret Policies
Deprecated alias of ``GET /bots/{bot_slug}/vault-entries``.