DealHub API

Name: DealHub API API
Brand: DealHub API
Availability: InStock

✓ Official Vendor SpecE CommerceOrder Managementbearer41 EndpointsREST

For Agents

Generate, simulate, submit, and publish CPQ quotes in DealHub, manage DealRooms and opportunities, and read pricing or billing data for an active deal.

Quickstart

Get started with DealHub API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"generate a DealHub quote"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with DealHub API API.

Simulate, generate, submit, and publish quotes through the /quotes endpoint family

Retrieve a quote document for sharing or attaching to a downstream contract

Read and update users and look them up by login through /users and /users/login/{login}

List and inspect DealHub product versions, including duplicating an existing version

GET STARTED

Start building with DealHub API API

Explore with Jentic

View OpenAPI Document

DealHub is a CPQ, CLM, and billing platform whose v2 API exposes 41 endpoints spanning quote generation, DealRoom collaboration, billing, opportunities, products, users, and version management. Quote workflows include simulate, generate, submit, and publish, supporting the full configure-price-quote lifecycle. The API uses bearer-token authentication and groups its surface under domain tags such as Quotes, Billing, DealRoom, Opportunities, Products, and Users for predictable navigation.

Use Cases

Patterns agents use DealHub API API for, with concrete tasks.

★ End-to-end CPQ quote generation

Sales teams using DealHub need to move from configuration to a delivered quote document without manual intervention. The API supports this with /quotes/simulate for pre-flight pricing, /quotes/generate to materialise the quote, /quotes/submit for approval routing, /quotes/publish for finalisation, and /quotes/{id}/document to retrieve the rendered output. Chaining these lets a workflow produce a customer-ready PDF straight from a CRM trigger.

POST /quotes/simulate with the configuration, POST /quotes/generate, POST /quotes/submit for approval, then GET /quotes/{id}/document once status is published.

User and identity reconciliation

Larger DealHub tenants integrate with an external identity provider and need to keep DealHub's user records in sync. GET /users lists the directory, /users/{id} returns an individual record, /users/login/{login} maps an SSO login back to the DealHub user, and PUT /users updates them in bulk. This is the foundation for provisioning workflows that drive DealHub from an HRIS or IdP.

GET /users/login/{login} to resolve the SSO id, then PUT /users with the updated profile fields.

Version management for product catalogues

DealHub product catalogues evolve through versions. /versions lists them, /versions/{id} retrieves details, /versions/name/{name} resolves a known version label, and POST /versions/duplicate clones an existing version as a starting point for the next iteration. This pattern is useful when a pricing change needs a new effective-dated version without disturbing live quotes.

GET /versions/name/{name} to find the source version, then POST /versions/duplicate to create a new editable copy.

AI agent driving DealHub quotes through Jentic

An agent triaging an opportunity from a CRM can search Jentic for 'generate a DealHub quote', call /quotes/simulate to validate pricing, and only proceed to /quotes/generate and /quotes/publish if the totals look right. The bearer token never enters the agent's context — Jentic attaches it at execution time — so the agent stays focused on the deal logic.

Search Jentic for 'generate a DealHub quote', call /quotes/simulate, then /quotes/generate, /quotes/submit, and /quotes/publish in sequence and return the document URL.

Key Endpoints

41 endpoints — dealhub is a cpq, clm, and billing platform whose v2 api exposes 41 endpoints spanning quote generation, dealroom collaboration, billing, opportunities, products, users, and version management.

METHOD

PATH

DESCRIPTION

POST

/quotes/generate

Generate a quote

POST

/quotes/simulate

Simulate a quote without persisting

POST

/quotes/submit

Submit a quote for approval

POST

/quotes/publish

Publish a quote

GET

/quotes/{id}

Retrieve a quote by id

GET

/quotes/{id}/document

Get the rendered quote document

GET

/users/login/{login}

Look up a user by login

POST

/versions/duplicate

Duplicate an existing version

POST

/quotes/generate

Generate a quote

POST

/quotes/simulate

Simulate a quote without persisting

POST

/quotes/submit

Submit a quote for approval

POST

/quotes/publish

Publish a quote

GET

/quotes/{id}

Retrieve a quote by id

GET

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The DealHub bearer token is stored encrypted in the Jentic vault (MAXsystem). Agents execute operations through Jentic and the Authorization: Bearer header is applied at call time — the raw token never enters the agent's context window.

Intent-based discovery

Agents search Jentic by intent (e.g., 'generate a DealHub quote' or 'duplicate a DealHub version') and receive the matching operation with its input schema, sparing the agent from navigating DealHub's 41 endpoints by hand.

Time to first call

Direct DealHub integration: 3-5 days to wire up bearer auth, the multi-step quote lifecycle, and version reconciliation. Through Jentic: under 2 hours — search, load, execute the chained calls.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Salesforce API

CRM that DealHub commonly sits next to for opportunity and account data.

Use alongside DealHub when the opportunity record lives in Salesforce and the quote should be triggered from a CRM action.

Alternative

PandaDoc API

Document automation platform with quoting and e-signature in one stack.

Choose PandaDoc when you need an integrated quote-plus-signature workflow rather than DealHub's CPQ-led CLM.

Complementary

Ironclad API

Contract lifecycle management for the redlining and signature stages downstream of CPQ.

Pair with DealHub when negotiation and signature happen in Ironclad after the quote is generated.

FAQs

Specific to using DealHub API API through Jentic.

What authentication does the DealHub API use?

DealHub uses bearer-token authentication on every endpoint. Through Jentic the token is held in the encrypted vault and added to the Authorization header at execution time, so the raw token never enters the agent's context.

Can I simulate a DealHub quote before generating it?

Yes. POST /quotes/simulate runs the pricing engine without creating a persisted quote, which is the recommended pre-flight before /quotes/generate. Simulating first avoids cluttering the quote list with abandoned drafts when an agent is iterating.

How do I retrieve the rendered document for a DealHub quote?

Once a quote has been generated and ideally published, GET /quotes/{id}/document returns the rendered output. Pair this with /quotes/{id} to confirm the status before fetching the document so you don't pull a stale draft.

What are the rate limits for the DealHub API?

The OpenAPI spec does not document explicit rate limits. Treat /quotes/simulate as the cheaper iteration step and reserve /quotes/generate for the final pricing the customer will see.

How do I generate and publish a DealHub quote through Jentic?

Run pip install jentic, search for 'generate a DealHub quote', and Jentic returns the /quotes/generate operation with its input schema. Load it, supply the configuration, execute, then call /quotes/submit and /quotes/publish in turn. Jentic handles the bearer header on every call.

Does the DealHub API expose contract redlining or e-signature endpoints?

No dedicated redlining or e-signature endpoints are present in this v2 spec. The API covers quote generation, DealRoom workspaces, opportunities, billing, users, products, and versions. Pair with a dedicated e-signature platform when signature capture is required.