Create a proactive trigger

Optional. Choose a unique value per intended creation and send it again on every retry of that same request: the API then returns the stored first response, marked Idempotency-Replayed: true, instead of creating a second resource. Stored for 24 hours per account and route. The request body is compared byte for byte: the same key with a different body (even a different key order) gives 422. The same key while the first request is still running gives 409 with Retry-After. 5xx responses are not stored; the key is released. POST /api/v1/chatbots/{id}/chat accepts the header only with stream: false — with stream: true (the default) it answers 400 before anything is stored.