Skip to content
Company & B2B

Job Change Monitoring

A webhook event when a watched contact changes company or title.

POST/v1/job-change-monitoring
5 credits / checkBulk supportedGlobal
Request
curl -X POST https://api.1lookup.dev/v1/job-change-monitoring \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"linkedin_url":"https://www.linkedin.com/in/jordan-avery-example","frequency":"monthly"}'
Response
{
  "success": true,
  "data": {
    "monitor_id": "mon_4t9x2k7c",
    "linkedin_url": "https://www.linkedin.com/in/jordan-avery-example",
    "frequency": "monthly",
    "status": "active",
    "last_checked_at": "2026-11-01T06:00:00Z",
    "next_check_at": "2026-12-01T06:00:00Z",
    "change_detected": true,
    "change": {
      "type": "company_change",
      "detected_at": "2026-11-01T06:00:00Z",
      "previous": {
        "title": "Director of Revenue Operations",
        "company": "Northwind Logistics"
      },
      "current": {
        "title": "VP of Revenue Operations",
        "company": "Fabrikam Health",
        "started": "2026-10"
      }
    }
  },
  "meta": {
    "credits_used": 5,
    "credits_remaining": 999,
    "cached": false,
    "request_id": "req_8f3a2c1e9b7d"
  }
}

Authorization

Authorizationstring<bearer>required

Your API key as a Bearer token. Live keys start with 1lk_live_. Test keys start with 1lk_test_ and return this endpoint's sample response without spending credits. See authentication.

Body

Send the fields as a JSON object with Content-Type: application/json.

linkedin_urlstring<uri>required

LinkedIn profile URL. Example: https://www.linkedin.com/in/jordan-avery-example

frequencyenum<string>required

Check frequency. One of: weekly, monthly, quarterly. Example: monthly

freshboolean

Skip the 7-day cache and run a new lookup. Charged as a normal lookup.

referencestring

Your own identifier, echoed back in meta and shown in lookup history.

Response

A 200 response carries the result in data and the cost of the call in meta. These are the fields most integrations read.

successboolean

true when the lookup ran.

data.statusstring

Whether the contact is being monitored.

data.frequencystring

How often the contact is checked: weekly, monthly or quarterly.

data.last_checked_atstring

When the latest scheduled check ran.

data.next_check_atstring

When the following check is due.

data.change_detectedboolean

True when the last check found a new company or title.

data.change.typestring

company_change for a move to a new employer, title_change for a new role at the same one.

data.change.previousobject

The title and company on record before the change.

data.change.currentobject

The title and company found at the check, with a start date when available.

meta.credits_usednumber

Credits charged for this call.

meta.credits_remainingnumber

Your balance after the call.

meta.cachedboolean

true when the result came from the 7-day cache.

meta.request_idstring

Quote this when you contact support.

Errors

A failed request returns success: false with an error object, and is never charged. The full list is on the errors page.

HTTPCodeMeaning
401unauthorizedThe key is missing, malformed or revoked.
402insufficient_creditsYour credits are used up and pay as you go is off or at its limit.
422invalid_inputA field is missing or malformed. The field property names it.
429rate_limitedToo many requests for this key. Wait for the Retry-After interval.
500internal_errorSomething failed on our side. Safe to retry.
503source_unavailableAn upstream source did not answer in time. Safe to retry.

Billing

5 credits / check. Charged when the lookup runs and returns a result. Errors are never charged, and repeating the same input within 7 days is served from cache at no charge.

Product overview and use cases