---
title: "Trigger Nightly Batch"
method: POST
path: "/api/admin/memory/{user_id}/nightly"
tags: ["v2", "admin", "admin", "memory"]
---

# Trigger Nightly Batch

`POST /api/admin/memory/{user_id}/nightly`

Fire the full nightly batch fan-out and return 202 + job_id immediately.

Frontend polls ``GET /api/admin/memory/{user_id}/nightly/{job_id}``
for progress. Same composition as the 03:00 cron — every enabled
batch-family submitter runs in sequence sharing one ``nightly_id``
for cost-log attribution.

## Path parameters

- `user_id` string, required — User id or 'me'

## Response `202`

Successful Response

- JobTriggerResponse — 202 response from a fire-and-forget admin trigger. Frontend captures ``job_id`` and polls ``GET .../{job_id}`` for progress. ``state`` is always ``"queued"`` at this point — the scheduler picks the job up within sub-second and flips it to ``running``.
  - `job_id` string, required
  - `user_id` string, required
  - `kind` 'nightly' | 'dream_pass' | 'rebuild', required
  - `state` 'queued' | 'running' | 'submitted' | 'complete' | 'errored', required
  - `started_at` string, date-time, required

## Other responses

- `401` — Authentication required
- `422` — Validation Error

---

[API](https://skmtc.net/significant-gravitas/apis/autogpt-agent-server.md) · [All operations](https://skmtc.net/significant-gravitas/apis/autogpt-agent-server/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/significant-gravitas/autogpt-agent-server/versions/382041c7ecb2/schema)