---
title: "Campaign Detail"
method: GET
path: "/campaigns/detail/{agent_module_id}"
tags: ["authenticated", "campaigns"]
---

# Campaign Detail

`GET /campaigns/detail/{agent_module_id}`

## Request

- Base URL: `https://api-docs.upsmith.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api-docs.upsmith.com/campaigns/detail/{agent_module_id}`
- Auth: one of:
  - API key in header `x-api-key`
  - HTTP bearer

Return per-variant detail for a specific agent module's campaigns.

When the input ``agent_module_id`` resolves to a known JTBD roster name
(Mollie / Mary / etc.), the variant list expands to include every
campaign in the org under that roster — across both the v1
``agent_module`` and v2 ``agent_v2`` records the homepage groups
together. So clicking into "Mollie" surfaces the full picture, not
just whichever variant ``agentModuleIdMap`` happened to pick first.

## Path parameters

- `agent_module_id` string, required

## Query parameters

- `date` string, date, nullable
- `range` string, nullable

## Headers

- `organization-id` string, nullable
- `x-user-id` string, nullable
- `timezone` string
- `x-actor-email` string, nullable
- `x-request-source` string, nullable
- `x-operation-id` string, nullable
- `x-commit-message` string, nullable
- `x-confirmation-id` string, nullable
- `x-chat-id` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/upsmith/apis/upsmith-api.md) - [All operations](https://skmtc.dev/upsmith/apis/upsmith-api/llms.txt) - [OpenAPI document](https://skmtc.dev/upsmith/apis/upsmith-api/revisions/cce8b07a5787?raw)
