---
title: "Stop Alignment"
method: POST
path: "/api/v3/alignment-projects/{alignment_id}/stop"
tags: ["Alignment Projects"]
---

# Stop Alignment

`POST /api/v3/alignment-projects/{alignment_id}/stop`

## Request

- Base URL: `https://api.nugen.in`
- URL: `https://api.nugen.in/api/v3/alignment-projects/{alignment_id}/stop`
- Auth: HTTP bearer

Stop an in-progress train-time alignment.

**Path Parameters:**
- `alignment_id`: Alignment project identifier

**Returns:**
- `alignment_id`: ID of the stopped alignment project
- `status`: New status

**Raises:**
- `400`: If the alignment is already in a terminal state or has not started train-time alignment yet
- `404`: If the alignment project is not found or does not belong to the user
- `502`: If the train GPU server rejected the stop request
- `503`: If the train GPU server is unreachable

## Path parameters

- `alignment_id` string, required

## Response `200`

Stops an in-progress train-time alignment and marks the alignment project as STOPPED.

- AlignmentProjectStopResponse: Confirmation that an alignment project was stopped.
  - `alignment_id` string, required: Identifier of the stopped alignment project.
  - `status` 'QUEUED' | 'PROCESSING' | 'READY' | 'FAILED' | 'STOPPED', required: Lifecycle status of a resource that runs asynchronously. Stored as is and returned as is, with no translation in between. - `QUEUED`: accepted and waiting for its workflow to start - `PROCESSING`: running - `READY`: finished successfully - `FAILED`: failed at any stage - `STOPPED`: stopped by the user before completion

## Other responses

- `401`: Invalid API key
- `403`: Authorization header missing or not a Bearer token
- `404`: Resource not found
- `422`: Validation Error

---

[API](https://skmtc.dev/nugen/apis/nugen-intelligence-api.md) - [All operations](https://skmtc.dev/nugen/apis/nugen-intelligence-api/llms.txt) - [OpenAPI document](https://skmtc.dev/nugen/apis/nugen-intelligence-api/revisions/62baa7960a4a?raw)