Contacts Discover Generate

Changed on

Dispatch a BYOK DiscoGen task that discovers contacts at each given company domain.

Builds a test_discogen_prompt.py-style multi-row query ("Find X. Return A | B | C per line.") from the ICP text. DiscoGen auto-detects the response format and runs the query per-domain with web search enabled. Poll GET /discogen/status/{task_id} for results.

BYOK: uses the caller's own LLM and search provider keys. DiscoLike does not bill per contact returned. Results may include hallucinated personas - callers must treat email, linkedin_url, and other identifying fields as candidate data until validated.

Discovery leaves email null unless a source shows it verbatim. With find_emails=true the task then runs the email finder over every named, email-less row and fills email / email_status before completing; found addresses bill under the finder's own rules.

post/contacts/discover/generate

Request

  • Base URL
    https://api.discolike.com (the document declares no server; this is the origin it was published from)
  • Auth
    • API key in header X-API-Key
    • or HTTP bearer

Request body

icp_textstring required

ICP / persona description of the contacts to find.

domainsstring[] required

Company domains to search at (1-10000).

context_mode'website' | 'profile' | 'domain'
integration_idstring nullable

LLM provider integration UUID, or 'native' for keyless extraction without title validation. Omit for native when it is available and a search provider resolves (the org default, or its only one), else the org default LLM.

search_provider_idstring nullable
search_context_size'low' | 'medium' | 'high'
max_contacts_per_domaininteger
max_company_recordsinteger nullable
full_domainsstring[] nullable
partial_domainsstring[] nullable
initial_contact_countsobject nullable
find_emailsboolean

After discovery, run every contact that has a name but no email through the email finder (same as the app's Verify step) and fill email / email_status on the row before the task completes. Found addresses are billed under the finder's own rules; nothing else is.

Response

Successful Response

task_idstring required

Unique task identifier for polling status

status'in_progress' required

Task status: in_progress

total_domainsinteger required

Total number of domains to process

Changes