--- search: tags: - Integrations - POST seo: description: >- Resolve creatives by either handle: the campaign… Reference for the POST /api/v1/integrations/creative-tests/creatives/lookup endpoint in the Kumquat API API. sidebar: badge: POST label: Lookup Creatives title: Lookup Creatives type: openapi-operation --- Resolve creatives by either handle: the campaign a name ran in, or the names a campaign covers. Both directions of what `POST /creatives/launched` and `POST /packs/launched` recorded. A POST because it reads a batch — up to 500 names and 500 campaign ids per call, more than a URL holds, and the `ad_id` half costs one query per call rather than one per id. Rows come back in the order asked, names first and campaign ids after, one row per handle naming what it resolved to. Never a 404: a handle nothing carries gets an empty `creatives` in its own row, and 422 stays for what the client got wrong — a blank handle, a batch over the cap, a body naming neither list. The packs are read once for the whole batch, not per row: they carry `varied_elements`, which no creative has a field for, and they are what a card minted before the rollup falls back to. The task owner and assignee are resolved the same way, one read of the user directory per batch.