# Watch USDOT Contact Changes

**Use case:** 

Use the same snapshot key after the baseline exists. The dataset lists phone, email, officer, name and address changes. An empty dataset means nothing material changed. The run summary still counts unchanged carriers.

## Input

```json
{
  "usdotNumbers": [
    "264184",
    "54283",
    "53467"
  ],
  "snapshotKey": "approved-carriers",
  "emitUnchanged": false,
  "includeBaseline": true
}
```

## Output

```json
{
  "usdotNumber": {
    "label": "Usdot number"
  },
  "status": {
    "label": "Status"
  },
  "attentionLevel": {
    "label": "Attention level"
  },
  "changeTypes": {
    "label": "Change types"
  },
  "changeClasses": {
    "label": "Change classes"
  },
  "changes": {
    "label": "Changes"
  },
  "observedAt": {
    "label": "Observed at"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The FMCSA Carrier Contact Takeover Monitor Actor is ready to run with the inputs already set for "Watch USDOT Contact Changes". [Sign up or log in](https://console.apify.com/create-task-from-example/OR0aNPMevNs7iE5AI) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Watch USDOT Contact Changes" task

The FMCSA Carrier Contact Takeover Monitor Actor will start running based on the input automatically. You can also change all the input fields, like USDOT numbers, snapshot key, and more, to match your specific use case.

### 3. Receive the "Watch USDOT Contact Changes" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as usdot number, status, attention level, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Watch USDOT Contact Changes" task via API](https://apify.com/automa-flow/fmcsa-carrier-contact-takeover-monitor.md).

## About this Actor

This example demonstrates how to use [FMCSA Carrier Contact Takeover Monitor](https://apify.com/automa-flow/fmcsa-carrier-contact-takeover-monitor.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/automa-flow/fmcsa-carrier-contact-takeover-monitor.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/automa-flow/fmcsa-carrier-contact-takeover-monitor.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).