---
title: "Autopilot Tick"
method: POST
path: "/api/v2/app/autopilot/tick"
tags: ["v2-app"]
---

# Autopilot Tick

`POST /api/v2/app/autopilot/tick`

## Request

- Base URL: `https://api.getle.ad` (the document declares no server; this is the origin it was published from)
- URL: `https://api.getle.ad/api/v2/app/autopilot/tick`
- Auth: none declared

Review every opted-in account's campaigns and act on the results.

Same shared-secret guard as /send/tick, and the same reason: this is a cron
target, not something a browser session calls, and a public one would let
anyone pause or rebalance an account's campaigns.

This route existing does not by itself mean it runs on a schedule - it has
to be wired to an actual scheduler (a Railway cron hitting this endpoint, or
equivalent) as a separate deploy step. Calling it directly runs one real
review pass right now, which is how it was tested.

## Request body

- AutopilotTickRequest
  - `worker_token` string, required
  - `account_id` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/getle/apis/lead-generator-pro-api.md) · [All operations](https://skmtc.dev/getle/apis/lead-generator-pro-api/llms.txt) · [OpenAPI document](https://skmtc.dev/getle/apis/lead-generator-pro-api/revisions/041155e6d905?raw)