---
title: "Alpha Regrade Due"
method: POST
path: "/v1/me/accounts/{account_id}/alphas/{deploy_id}/regrade-due"
---

# Alpha Regrade Due

`POST /v1/me/accounts/{account_id}/alphas/{deploy_id}/regrade-due`

## Request

- Base URL: `https://api.quantradin.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.quantradin.com/v1/me/accounts/{account_id}/alphas/{deploy_id}/regrade-due`
- Auth: none declared

RE-GRADE APPOINTMENT (R9, 2026-09-23) — move this bot's re-grade date,
or clear it with null.

A SHADOW/SHELF grade books one automatically (``jobs.run_alpha_backtest``
is still the only path that writes a deployment's grade). This is how the
member says "not then, then" or "stop reminding me" — both are answers we
take. Setting a date marks the appointment as THEIRS, so a later grade
refreshes the REASON and leaves their date alone; clearing removes the
whole appointment, including the nudge.

It gates NOTHING. The bot trades identically with an appointment, past
one, or with none — the engine advises, it never gates. No new column:
the date rides ``config`` (jsonb). Owner/desk-pair scoped (404 cross-desk,
via _owned_deployment), audited like the other per-bot edits.

## Path parameters

- `account_id` integer, required
- `deploy_id` string, required

## Request body

- RegradeDueRequest: THE APPOINTMENT IS THE MEMBER'S (2026-09-23). ``due`` is an ISO ``YYYY-MM-DD``; null CLEARS the appointment entirely. It is a date to come back on, never a gate: nothing about the bot changes when it passes, and a bot with no appointment trades exactly like one that has kept it.
  - `due` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/quantradin/apis/vega-api.md) · [All operations](https://skmtc.dev/quantradin/apis/vega-api/llms.txt) · [OpenAPI document](https://skmtc.dev/quantradin/apis/vega-api/revisions/47add154ef38?raw)