---
title: "Force-start an autopilot search"
method: POST
path: "/v3/sequences/ai-sdr/{sequence_id}/autopilot/force-start"
tags: ["AI SDR Sequences"]
---

# Force-start an autopilot search

`POST /v3/sequences/ai-sdr/{sequence_id}/autopilot/force-start`

<Warning>
  **Coming soon.** This endpoint will be available by early July 2026.
</Warning>

<small>_Requires the `ai-sdr:operate` scope (or a broader one that includes it)._</small>

Force-starts an autopilot contact search for the sequence, bypassing the normal schedule. Autopilot must already be enabled; rejected with 409 otherwise.

Requires the AI SDR feature on the caller's team.

## Path parameters

- `sequence_id` integer, required

## Response `204`

Autopilot search started

## Other responses

- `400` — Sequence is not an AI SDR sequence, or current autopilot filters are invalid.
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `403` — AI SDR feature is not available for the caller's team, or the caller does not have access to this sequence.
- `404` — Sequence not found.
- `409` — Autopilot is not enabled (including when it was auto-disabled because the contacts limit was exceeded or no matching contacts were found), or an autopilot search is currently throttled.
- `502` — Upstream AI SDR service failure.

---

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