Queue a planned fine-tuning job
POST
/v1/fine-tuning/jobs/{jobId}/queueIdempotently transitions a provisioned planned optimization job to queued and creates its execution dispatch. This is the explicit handoff used after upstream Test and Evaluation gates pass.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| jobId | path | string | Yes | — |
Query parameters
None.
Body schema
Content type: application/json · Optional
| Field | Type | Required | Description |
|---|---|---|---|
| source | string | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Job was already queued or executing
None.
202Planned job was queued
None.
409Job is not in a queueable state
None.