---
title: "Create a list"
method: POST
path: "/lists/list"
tags: ["Lists"]
---

# Create a list

`POST /lists/list`

## Request

- Base URL: `https://api.emelia.io`
- URL: `https://api.emelia.io/lists/list`
- Auth: API key in header `Authorization`

Creates an empty list with source `API` and status `mapped`, immediately ready to receive contacts through `POST /lists/list/{listId}/contacts` or the batch route. List names do not need to be unique: calling this twice creates two lists, so store the returned `listId`.

To make the contacts of the list enter a campaign, attach the list to the campaign (in the app or through the Campaigns API). Contacts added afterwards flow into the campaigns that use the list.

Do not send `source`: the value `Manual` is reserved to the web app and starts the list with most columns hidden, which removes their fields from `GET /lists/list/{listId}/rows` until contacts fill them.

## Request body

- object
  - `name` string, required: List name, trimmed. Must not be empty.

## Response `201`

List created.

- ListsCreateListResult
  - `success` true, required
  - `listId` string, required
  - `name` string, required

## Other responses

- `401`: Missing, unknown or disabled API key, or the account of the key no longer exists. Note the body shape: `error` and `code`, not `message`.
- `422`: Missing or empty name.
- `500`: Unexpected server error. `error`, when present, is a raw internal message: do not parse it. Retry later.

---

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