---
title: "Launch Segment"
method: POST
path: "/api/app-auto-gtm/segments/{segment_id}/launch"
tags: ["AppAutoGtm"]
---

# Launch Segment

`POST /api/app-auto-gtm/segments/{segment_id}/launch`

Prepare a segment for launch: apply budget (+ optional target_url).

The agent session itself is still created by the client via
`POST /api/agent-chat/sessions` — we don't want to spawn a Claude CLI
subprocess from this request. Keeping the split lets the client flow
stay unchanged while this endpoint takes care of the one-shot writes
(budget + target_url) that used to leak across the 2-3 calls
of onboarding/MiniOnboarding.

`target_url` is not required here — discovery/research runs fine without
it. Outreach workers must gate on a non-empty value separately; the UI
gates the Launch button so most callers will supply it.

## Path parameters

- `segment_id` integer, required

## Cookies

- `ex_access` string, nullable
- `ex_org` string, nullable

## Request body

- LaunchSegmentRequest
  - `daily_limit_usd` integer, required
  - `target_url` string, nullable

## Response `200`

Successful Response

- LaunchSegmentResponse
  - `segment_id` integer, required

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/explee/apis/explee-api.md) · [All operations](https://skmtc.dev/explee/apis/explee-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/explee/explee-api/revisions/f169bc6e9447/schema)
