---
title: "Enroll contacts in an active automation"
method: POST
path: "/automations/{id}/enroll"
tags: ["Automations"]
---

# Enroll contacts in an active automation

`POST /automations/{id}/enroll`

## Request

- Base URL: `https://sending.dev/api/v1`
- URL: `https://sending.dev/api/v1/automations/{id}/enroll`
- Auth: HTTP bearer

Adds contacts to an automation without waiting for the trigger: they enter at the start of the flow and the steps that send really send. Provide ONE audience among `listId`, `segmentId` and `contactIds`. Works only on `active` automations (409 on drafts and paused automations). Enrollment is asynchronous: the 202 says it was queued, per-contact outcomes are in the step log. A contact who is already enrolled is ignored (once-per-contact). Required scope: `automations:write`.

## Path parameters

- `id` string, required: Automation ID.

## Request body

- AutomationEnrollRequest
  - `listId` string, uuid
  - `segmentId` string, uuid
  - `contactIds` string[]

## Response `202`

Enrollment queued.

- AutomationEnrollQueued
  - `id` string, uuid, required
  - `queued` boolean, required
  - `audience` string, required

## Other responses

- `401`: Missing or invalid token.
- `403`: Insufficient scope.
- `404`: Resource not found.
- `409`: State conflict (e.g. duplicate).
- `422`: Invalid input.

---

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