Release a fine-tuning job execution lease

DELETE/v1/fine-tuning/jobs/{jobId}/lease

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
NameLocationTypeRequiredDescription
jobIdpathstringYes—
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
ownerstringYes—
tokenstringYes—

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Released leaseapplication/json
FieldTypeRequiredDescription
releasedtrueYes—
jobobjectYes—
job.schemaVersionintegerNo—
job.kindagent_optimizationNo—
job.idstringYesUnique identifier.
job.namestringNoHuman-readable name.
job.agentIdstringYesAgent ID.
job.targetAgentIdstringNo—
job.environmentIdstringNoComputer ID.
job.computerIdstringNo—
job.evaluationSetIdsstring[]Yes—
job.instructionsstringNo—
job.statusplanned | queued | running | verifying | completed | failed | cancelledYesCurrent lifecycle status.
job.phasestringNo—
job.threadIdstringNoThread ID.
job.createdAgentVersionIdstringNo—
job.beforeScorenumberNo—
job.afterScorenumberNo—
job.improvementScorenumberNo—
job.costUsdnumberNo—
job.costCtnumberNo—
job.costTokensnumberNo—
job.evaluationRunsobject[]No—
job.metadataobjectNoFree-form metadata object.
job.createdAtstringNoISO 8601 timestamp.
job.updatedAtstringNoISO 8601 timestamp.
job.completedAtstringNoISO 8601 timestamp.
409Lease credentials are stale
None.
Release a fine-tuning job execution lease
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow