canonical: https://jentic.com/apis/platform.dealpath.com/dealpath

# Platform Dealpath Dealpath Developer API

Comprehensive information for integrating with our API endpoints. The API exposes 90 endpoints secured with bearer authentication.

## For AI agents

Programmatically creates and returns a new asset., updates an asset and returns it.. Covers 90 operations with bearer authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Creates and returns a new asset.
- Updates an asset and returns it.
- Deletes an asset and returns its ID.
- Returns a paginated list of assets.

## Use cases

### CRM Operations

Use the Dealpath Developer API to perform crm operations programmatically. The API provides 90 endpoints covering core functionality including creates and returns a new asset., updates an asset and returns it., deletes an asset and returns its id..

Example prompt: Call POST /asset to creates and returns a new asset.

### Automated Assets Management

Automate assets operations by combining multiple Dealpath Developer API endpoints. Agents can updates an asset and returns it. and then deletes an asset and returns its id. in a single workflow.

Example prompt: Call PUT /asset/{asset_id} to updates an asset and returns it., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Dealpath Developer API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'creates and returns a new asset.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /asset | Creates and returns a new asset. |
| PUT | /asset/{asset_id} | Updates an asset and returns it. |
| DELETE | /asset/{asset_id} | Deletes an asset and returns its ID. |
| GET | /assets | Returns a paginated list of assets. |
| POST | /deal | Creates and returns a new deal. |
| GET | /deal/{deal_id} | Returns a deal. |
| PUT | /deal/{deal_id} | Updates a deal and returns it. |
| DELETE | /deal/{deal_id} | Deletes a deal and returns its ID. |

## Key resources

- **Assets** — Asset operations
- **Deals** — Deal operations
- **Field Definitions** — Field definition operations
- **Fields** — Field operations
- **Files** — Files operations

## Why Jentic

- **Setup:** Wiring the Dealpath Developer API by hand means learning its bearer auth and hand-building requests across its asset and deal endpoints yourself. Through Jentic you install once, import Dealpath from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Dealpath puts the resource id in the URL path (/asset/{asset_id}, /deal/{deal_id}), so a rule can pin your agent to one asset or deal: it reads and updates that record and nothing else. You choose the operations it may call, so destructive ones like deleting an asset or deal are not included unless you add them.
- **Credential handling:** Your Dealpath token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a new asset' or 'read a deal', and Jentic returns the matching Dealpath operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Dealpath Developer API use?

The Dealpath Developer API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I creates and returns a new asset. with the Dealpath Developer API?

Yes. Use the POST /asset endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Dealpath Developer API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I creates and returns a new asset. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates and returns a new asset.'. Jentic returns the matching Dealpath Developer API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Dealpath Developer API have?

The Dealpath Developer API exposes 90 endpoints covering assets, deals, field definitions operations.

### Can I limit what my agent is allowed to do with the Dealpath Developer API?

Yes. Because you run Jentic One yourself, your own rules decide which Dealpath operations and credentials the agent may use. Since Dealpath puts the resource id in the URL path, such as /asset/{asset_id} and /deal/{deal_id}, a rule can pin the agent to a single asset or deal so it reads and updates only that record. You also choose the operations it may call, so destructive ones like deleting an asset or deal stay out of reach unless you add them.