Buying Committee DealMap

Map the buying committee for a prospect company — stakeholder roles, org hierarchy, and top picks.

Read the current DealMap

Send a GET request to check if a buying committee map already exists for a product and company. This is a free operation.

curl "https://dealsurface.com/api/v1/dealmap?product_id=12&ticker=TRV" \
  -H "Authorization: Bearer $DEALSURFACE_API_KEY"

Generate or refresh the DealMap

If the DealMap is empty or stale, generate it with a POST request. The endpoint fetches the org chart and uses AI to assign buying committee roles to each stakeholder.

curl -X POST https://dealsurface.com/api/v1/dealmap/generate \
  -H "Authorization: Bearer $DEALSURFACE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"product_id": 12, "ticker": "TRV"}'

Caching and billing

The DealMap generation endpoint caches results to minimize costs:

Cached org chart — the org chart was already fetched recently. Annotations are recomputed but no charge.
Fresh org chart fetch — no cached org chart exists. A fresh fetch is performed. 10 credits charged.

Check the credits_charged and generation_source fields in the response to understand what happened.

Use force_refresh with caution

Setting force_refresh: true bypasses all caches and always charges 10 credits. Only use this when you know the cached data is stale and need fresh org chart data.

Stakeholder data fields

Each stakeholder includes:

full_name and title — the contact's name and position.
stakeholder_role — AI-assigned buying committee role (Economic Buyer, Decision Maker, Champion, Executive Sponsor, Evaluator, Blocker, etc.).
is_top_pick — whether this person is the recommended contact for their role.
level — seniority bucket (c_suite, vp, director, manager).
linkedin_url — direct LinkedIn profile link (when available).
annotation_reason — why this role was assigned.

Next steps

Pass a stakeholder to the outreach endpoint to generate a personalized message for that contact.

Ranking Prospects Crafting Outreach