interviews.update

Change an interview or record how it went

Request: PATCH/api/v1/interviews/{interviewId}
Scope required: interviews: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: interviews_update
Environment: Live and sandbox alike.
Request body: JSON.

What it does

Edits one interview: reschedule it, change its type or location, or write the `feedback` afterwards. A field you leave out keeps its current value and `null` clears one. Naming an `applicationId` moves the interview to another of your cards. Send the `ETag` from `interviews.get` as `If-Match` to be refused with 412 if it changed in between.

Parameters

Parameters this endpoint accepts, where each one goes, and whether it is required
Name	Sent in	Requirement	Accepts
interviewId	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

applicationId: string, optional
feedback: string or null, optional
location: string or null, optional
notes: string or null, optional
time: string or null, optional
type: one of: phone_screen, technical, behavioral, panel, take_home, video_call, in_person, other or null, optional

Response

applicationId: string, required
createdAt: string, required
feedback: string or null, required
id: string, required
location: string or null, required
notes: string or null, required
time: string or null, required
type: one of: phone_screen, technical, behavioral, panel, take_home, video_call, in_person, other or null, required
updatedAt: string, required

Examples

Write down how it went

Write down how it went — request

curl -s -X PATCH https://www.jobapplicationtracking.com/api/v1/interviews/iv_42 \
  -H "Authorization: Bearer $JAT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "feedback": "Went well; a follow-up is likely."
}'

Write down how it went — response

{
  "id": "iv_42",
  "applicationId": "app_123",
  "time": "2026-02-20T15:00:00.000Z",
  "type": "technical",
  "location": "Zoom",
  "notes": "Two hours, systems design.",
  "feedback": null,
  "createdAt": "2026-02-11T17:05:00.000Z",
  "updatedAt": "2026-02-11T17:05:00.000Z"
}