Start bandit
Changed onStart a draft bandit. Its targeting rule is published serving every arm equally, and each refresh then shifts traffic toward the arms that do best. The bandit starts exactly as it is configured; set it up with PATCH /api/v2/experiments/bandits/{bandit_id} first. It needs a flag, at least two arms, a subject type, a metric, and an exposure SQL model. The request is idempotent: a bandit that is already running still returns 204, so a retry after a timeout is safe. Stop is not idempotent. A start is blocked when the flag environment requires an approval or a pending change request touches the flag's targeting rules; retrying alone does not resolve an approval requirement. Bandits must be enabled for the organization.
Request
- Base URLhttps://api.datadoghq.com
- Auth
- API key in header DD-API-KEY and API key in header DD-APPLICATION-KEY
- or OAuth 2Authorization code/oauth2/v1/authorizeToken URL/oauth2/v1/tokenScopesproduct_analytics_experiments_write
Path parameters
The UUID of the bandit.
Response
The bandit is running. Get the bandit to read its status and active policy.
Changes
- warning
the optional response header
X-RateLimit-Limitremoved for the status429 - warning
the optional response header
X-RateLimit-Periodremoved for the status429 - warning
the optional response header
X-RateLimit-Remainingremoved for the status429
1 more change in this revision
- warning