sequences

Keep the rewrite and the lesson that wrote it

The agent's instructions take the lesson (its next version), and the rewrite becomes the noted contact's thread, marked Looks good, so it is what sends. Every thread of the sequence already marked Looks good keeps its words across the new version. The run stays open on the new version; threads written ahead under the old instructions that nobody read leave it, and are written again when opened. A rewrite is kept whole: slot_keys, when sent, must name every change. Repeating the call is a no-op.

post/sequences/{sequence_id}/agent/training/{session_id}/apply/

Request

  • Base URL: https://api.getoneprofile.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.getoneprofile.ai/sequences/{sequence_id}/agent/training/{session_id}/apply/
  • Auth: one of:
    • API key in header X-API-Key
    • HTTP bearer

Path parameters

sequence_idstring uuid required
session_idstring uuid required

Request body

expected_revisioninteger required
rewriteboolean
slot_keysstring[] nullable

Response

Successful Response

agent_idstring uuid required
applied_versioninteger nullable required
base_versioninteger required
created_atstring date-time required
errorstring nullable required
idstring uuid required
note_waitingboolean

A note was given while another contact was being written: its rewrite is worked out as soon as that write lands.

reviewed_idsstring[]

Every contact given Looks good or a note in this run, including ones that left the run to make room.

revisioninteger required
status'running' | 'reviewing' | 'proposing' | 'proposed' | 'completed' | 'abandoned' required

A session's phase, also used to resume its review screen.

Changes

No recorded changes to this operation across all 1 revision of this API.