---
title: "Integrations - Fullpath"
url: "https://docs.unified.to/integrations/fullpath"
description: "Build Fullpath integrations faster with our Unified API — CRM data, API key, real-time sync."
date: "2026-11-21T17:08:55.315Z"
updated: "2026-11-21T17:08:55.315Z"
---

# Fullpath integration

> What this integration supports through the Unified.to API, by object. Live data: `GET https://api.unified.to/unified/integration?type=fullpath` with your workspace API key (or Core MCP `list_unified_integrations` with `type: "fullpath"`). All integrations: https://docs.unified.to/integrations.md

## Overview

- **Type:** `fullpath`
- **Categories:** [CRM](https://docs.unified.to/crm/overview.md), [Passthrough](https://docs.unified.to/passthrough/overview.md)
- **Website:** https://www.fullpath.com
- **Vendor API docs:** https://developers.fullpath.com/
- **Launched:** 2026-11-19

## How end users connect

- **API key** entered by the end user: `API Key`, `Dealership ID`
    - Your Fullpath API key (a dealer key from Fullpath Customer Success, or a vendor key issued by Fullpath at data-integrations@fullpath.com).
    - The numeric Fullpath Dealership ID the key gives access to. It is part of every API request path.

## MCP tools

The Unified MCP server (https://docs.unified.to/mcp/core.md) gives an AI agent these tools for a Fullpath connection. Preview the catalog, with input schemas, without an API key: `https://mcp-api.unified.to/mcp?integration_type=fullpath` (or `GET https://api.unified.to/tools?integration_type=fullpath`).

| Tool | Object | Method |
| --- | --- | --- |
| `list_crm_contacts` | [crm_contact](#crm_contact) | list |
| `get_crm_contact` | [crm_contact](#crm_contact) | get |
| `list_crm_events` | [crm_event](#crm_event) | list |
| `list_crm_leads` | [crm_lead](#crm_lead) | list |

## Supported objects

| Object | Methods | Webhooks |
| --- | --- | --- |
| [crm_contact](#crm_contact) | list, get | none |
| [crm_event](#crm_event) | list | none |
| [crm_lead](#crm_lead) | list | none |
| [passthrough](#passthrough) | none | none |

Values below come from the integration's support data. "Required list filters" must be sent on list calls; "Required on create" fields must be sent when creating. Webhook events are `native` (pushed by the vendor) or `virtual` (polled by Unified.to). Anything not listed is not supported; an unsupported method returns `501`.

### crm_contact

- **Methods:** `list`, `get`
- **MCP tools:** `list_crm_contacts`, `get_crm_contact`
- **Webhooks:** none
- **List filters:** `list_limit`, `list_offset`, `list_query`
- **Readable fields:** `address`, `created_at`, `emails`, `first_name`, `id`, `last_name`, `name`, `telephones`
- **Writable fields:** none
- **Vendor objects:** `shopper`
- **Model:** https://docs.unified.to/crm/contact/model.md

### crm_event

- **Methods:** `list`
- **MCP tools:** `list_crm_events`
- **Webhooks:** none
- **List filters:** `list_lead_id`, `list_limit`, `list_offset`, `list_type`, `list_user_id`
- **Readable fields:** `call`, `contact_ids`, `created_at`, `email`, `id`, `lead_ids`, `meeting`, `note`, `task`, `type`, `updated_at`, `user_id`
- **Writable fields:** none
- **Vendor objects:** `activity`, `task`, `appointment`
- **Model:** https://docs.unified.to/crm/event/model.md

### crm_lead

- **Methods:** `list`
- **MCP tools:** `list_crm_leads`
- **Webhooks:** none
- **List filters:** `list_limit`, `list_offset`
- **Readable fields:** `address`, `created_at`, `emails`, `first_name`, `id`, `last_name`, `name`, `source`, `status`, `telephones`
- **Writable fields:** none
- **Vendor objects:** `lead`
- **Model:** https://docs.unified.to/crm/lead/model.md

### passthrough

- **Methods:** none
- **Webhooks:** none
- **Readable fields:** none
- **Writable fields:** none
