> ## Documentation Index
> Fetch the complete documentation index at: https://docs.autosnap.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Website Provider Changes

> How AutoSnap handles dealership website provider changes to ensure uninterrupted inventory data.

Dealerships periodically switch the company that hosts and manages their website. When this happens, the underlying inventory data source changes — new page structure, new APIs, new data formats. Without intervention, this would cause inventory imports to silently stop working.

AutoSnap monitors every active dealership and handles provider transitions automatically so your integration stays reliable.

## How It Works

AutoSnap runs a daily health check on every subscribed dealership. The system verifies that the current configuration is still returning inventory data. If a dealership's inventory data stops flowing, AutoSnap automatically investigates and takes corrective action.

### Outcome 1: Configuration Drift (Auto-Repaired)

Sometimes a website provider makes changes to their platform without the dealership switching providers entirely — for example, updating internal identifiers or restructuring their inventory feed. When this happens:

1. AutoSnap detects the configuration has drifted
2. The system automatically generates an updated configuration
3. The next scheduled import uses the corrected configuration
4. You receive a `dealer.config.auto_updated` webhook notification

**No action is required on your part.** Inventory data continues flowing without interruption.

### Outcome 2: Full Provider Change

When a dealership switches to an entirely different website provider (e.g., moving from one platform vendor to another):

1. AutoSnap detects the provider change
2. You receive a `dealer.provider.changed` webhook notification with details about the old and new provider
3. AutoSnap logs the change, but does **not** automatically reconfigure the dealership for the new provider
4. Manual reconfiguration via the [Setup Dealer](/api-reference/endpoints/setup-dealer) endpoint may be required to resume imports

### Outcome 3: Unresolvable Issue

In rare cases, a website change cannot be automatically resolved — for example, if the new site uses a provider we haven't encountered before, or the site is temporarily down. When this happens:

1. The health check fails silently (no webhook is fired)
2. Our team is alerted internally and will investigate manually
3. Resolution typically happens within 24 hours

## Webhook Events

Subscribe to these events to stay informed about provider changes. See [Webhooks](/concepts/webhooks) for setup instructions.

| Event                        | Description                                           | Action Required                                                                                             |
| ---------------------------- | ----------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| `dealer.config.auto_updated` | Minor configuration change detected and auto-repaired | None                                                                                                        |
| `dealer.provider.changed`    | Dealership switched to a different website provider   | Reconfigure via the [Setup Dealer](/api-reference/endpoints/setup-dealer) endpoint if imports do not resume |

<Note>
  There is no `dealer.health_check_failed` event. If the health check encounters an unresolvable issue, no webhook is fired — the failure is handled internally by the AutoSnap team.
</Note>

### Example: `dealer.provider.changed`

```json theme={null}
{
  "event": "dealer.provider.changed",
  "dealership_id": "dlr_8cfc0b00a98b",
  "data": {
    "dealer_name": "Bay Dodge",
    "website": "baydodge.net",
    "old_provider": "DealerInspire",
    "new_provider": "CarsCommerce",
    "detection_confidence": 0.95,
    "new_config": {"dealership_url": "https://baydodge.net", "inventory_type": "all"}
  }
}
```

### Example: `dealer.config.auto_updated`

```json theme={null}
{
  "event": "dealer.config.auto_updated",
  "dealership_id": "dlr_8cfc0b00a98b",
  "data": {
    "dealer_name": "Bay Dodge",
    "website": "baydodge.net",
    "provider": "CDK",
    "changes": {"site_id": "new_value"}
  }
}
```

## Data Continuity

When a provider change occurs, historical vehicle data is preserved. Vehicles that existed under the old provider remain in your inventory history. The new provider's vehicles are imported fresh, and the standard `vehicle.created` / `vehicle.removed` webhook events fire as expected.

Vehicle identity is tracked by VIN, so if the same physical vehicle appears under the new provider, it is recognized as the same vehicle rather than creating a duplicate.

## Health Check Schedule

Health checks run once daily. Combined with the standard import schedule (every 12 hours), this means a provider change is typically detected and resolved within 24 hours of occurring.

## Billing

Auto-repairs and provider change re-configurations are **not billed** to your account. Only dealership setups that you explicitly initiate via the [Setup Dealer](/api-reference/endpoints/setup-dealer) endpoint count toward your usage.

<Note>
  If you need to force a re-detection outside of the daily health check cycle, you can delete the dealership and set it up again via the API. This will trigger a fresh detection and configuration.
</Note>