Write a finished authoring job's cases into the suite
Writes the job’s drafts into the suite. A draft carrying unresolved blocking issues or proposed additions is skipped rather than written, and comes back under skipped with a reviewUrl for finishing it in the app.
A job whose source is markdown — the in-app upload — is not committable here and answers 404: those drafts exist so a person decides on them, and an API commit would decide on their behalf.
Authorizations
MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.
Path Parameters
ID of the hosted project that contains the server.
Eval suite ID, as returned by POST /eval-runs.
Body
Response
The cases written and any the commit skipped, or the job's own status when it finished without committing (failed, cancelled, or still pending at the end of the wait).
- Option 1
- Option 2
Cases the commit could not write, each with its reason. They stay on the job rather than being lost.
Opens the app on exactly the skipped drafts. Present only when something was skipped — finishing them there costs nothing, whereas re-sending the document re-authors and re-bills every case in it.

