interactions.get
Read one logged interaction
- Request
- GET
/api/v1/interactions/{interactionId} - Scope required
contacts:read- Effect
- Reads only. Safe to retry and safe for an agent to call unprompted.
- Acts on
- Acts on the account’s own job search.
- MCP tool
interactions_get- Environment
- Live and sandbox alike.
- Request body
- JSON.
What it does
Returns a single interaction with a contact: what kind it was, when it happened, and any note taken at the time. An interaction belonging to another account answers 404, never 403. The response carries a weak `ETag` for `interactions.update` to send back as `If-Match`. Find the id with `interactions.list`.
Parameters
| Name | Sent in | Requirement | Accepts |
|---|---|---|---|
| interactionId | path | Required | string |
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
An email to a recruiter
curl -s https://www.jobapplicationtracking.com/api/v1/interactions/ix_88 \
-H "Authorization: Bearer $JAT_KEY"{
"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"
}