Skip to main content

contacts.update

Change a contact

Request
PATCH/api/v1/contacts/{contactId}
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
contacts_update
Environment
Live and sandbox alike.
Request body
JSON.

What it does

Changes the fields you name on a contact and leaves the rest alone. Naming `companies` or `applicationIds` replaces that whole list rather than adding to it, so read the contact first with `contacts.get` and send the list you want to end up with. Send the `ETag` from that read as `If-Match` to be refused with 412 if the contact changed in between.

Parameters

Parameters this endpoint accepts, where each one goes, and whether it is required
NameSent inRequirementAccepts
contactIdpathRequiredstring
If-MatchheaderOptionalstring — The ETag of the version you read. The write is refused with 412 if the resource has changed since.

Request body

applicationIds
array of string, optional
category
string or null, optional
companies
array of object, optional
id
string or null, optional
name
string, required
email
string or null, optional
firstName
string, optional
lastName
string or null, optional
notes
string or null, optional
phone
string or null, optional
source
string or null, optional

Response

applications
array of object, required
companyName
string, required
id
string, required
title
string, required
category
string or null, required
companies
array of object, required
id
string, required
name
string, required
createdAt
string, required
email
string or null, required
firstName
string, required
id
string, required
lastName
string or null, required
notes
string or null, required
phone
string or null, required
source
string or null, required
updatedAt
string, required

Examples

Record where the introduction came from

Record where the introduction came from — request
curl -s -X PATCH https://www.jobapplicationtracking.com/api/v1/contacts/ct_42 \
  -H "Authorization: Bearer $JAT_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "source": "LinkedIn"
}'
Record where the introduction came from — response
{
  "id": "ct_42",
  "firstName": "Dana",
  "lastName": "Okafor",
  "email": "dana@acme.example",
  "phone": null,
  "category": "Recruiter",
  "source": "LinkedIn",
  "notes": "Owns hiring for the platform team.",
  "companies": [
    {
      "id": "co_42",
      "name": "Acme"
    }
  ],
  "applications": [
    {
      "id": "app_123",
      "title": "Staff Engineer",
      "companyName": "Acme"
    }
  ],
  "createdAt": "2026-01-04T09:30:00.000Z",
  "updatedAt": "2026-02-11T17:05:00.000Z"
}

Related operations