Approve a verified optimization candidate for publication
POST
/v1/fine-tuning/jobs/{jobId}/publication-approvalAtomically binds the authenticated reviewer to the current evidence fingerprint and transitions a manual-review job to server-controlled publication.
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 · Required
| Field | Type | Required | Description |
|---|---|---|---|
| evidenceFingerprint | string | Yes | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Publication was already approved
None.
202Publication approval recorded
None.
409Job or evidence is no longer eligible for approval
None.
Approve a verified optimization candidate for publication
Loading...
Response 200
Loading...