interactions.update
Correct a logged interaction
- Request
- PATCH
/api/v1/interactions/{interactionId} - Scope required
contacts:write- Effect
- Changes data. Send an Idempotency-Key if you might retry it.
- Acts on
- Acts on the account’s own job search.
- MCP tool
interactions_update- Environment
- Live and sandbox alike.
- Request body
- JSON.
What it does
Changes the kind, the note or the time of an interaction already logged; a field you leave out is left alone. The contact it belongs to cannot be changed — delete it with `interactions.delete` and log it again against the right person. Send the `ETag` from `interactions.get` as `If-Match` to be refused with 412 if it changed in between.
Parameters
| Name | Sent in | Requirement | Accepts |
|---|---|---|---|
| interactionId | path | Required | string |
| If-Match | header | Optional | string — The ETag of the version you read. The write is refused with 412 if the resource has changed since. |
Request body
- interactionTime
- string, optional
- notes
- string or null, optional
- type
- one of: call, direct_message, email, follow_up, job_fair, meeting, networking_event, recruiter_outreach, reference_check, referral, social_media, thank_you_note, other, optional
Response
- contactId
- string, required
- createdAt
- string, required
- id
- string, required
- interactionTime
- string, required
- notes
- string or null, required
- type
- one of: call, direct_message, email, follow_up, job_fair, meeting, networking_event, recruiter_outreach, reference_check, referral, social_media, thank_you_note, other, required
- updatedAt
- string, required
Examples
Fix the note taken during a call
curl -s -X PATCH https://www.jobapplicationtracking.com/api/v1/interactions/ix_88 \
-H "Authorization: Bearer $JAT_KEY" \
-H "Content-Type: application/json" \
-d '{
"notes": "Asked about the timeline for the platform team role."
}'{
"id": "ix_88",
"contactId": "ct_42",
"type": "email",
"notes": "Asked about the timeline for the platform team role.",
"interactionTime": "2026-02-10T15:00:00.000Z",
"createdAt": "2026-02-10T15:04:00.000Z",
"updatedAt": "2026-02-10T15:04:00.000Z"
}