Endpoint
Request
Headers
Name | Type | Required | Description |
---|---|---|---|
x-api-key | string | Yes | Your Sixtyfour API key |
Content-Type | string | Yes | Must be application/json |
Body
Field | Type | Required | Description |
---|---|---|---|
target_company | object | Yes | Company data to enrich |
struct | object | Yes | Fields to collect |
find_people | boolean | No | Whether to find people associated with the company |
research_plan | string | No | Optional research plan to guide enrichment |
people_focus_prompt | string | No | Description of people to find, typically includes the roles or responsibilities of the people you’re looking for |
Example Request
Response
Deprecated field: findings
Thefindings
field is deprecated. It currently returns an empty list and will be removed in a future update.
Success Response (200)
Returns enriched company data including leads if requested.Error Response (400)
Async Endpoint
For longer-running enrichment tasks, you can use the async endpoint to submit a job and retrieve results later.Start Async Job
Request
The request format is identical to the synchronous endpoint.Response
Returns a task ID that can be used to check job status and retrieve results.Check Job Status
Response
Pending/Processing:Example Async Usage
Type Casting
The API automatically handles type casting for structured data output with intelligent type preservation and conversion.Type Priority Order
- Explicit Type Definitions (Highest Priority) - Specified in
struct
field definitions - Original Input Types - Types from
target_company
when not explicitly overridden - Inferred Types - From example values in
struct
- Default to String (Lowest Priority)
Supported Types
Type | Example Values |
---|---|
"str" or "string" | "Pacific View Studios" |
"int" or "integer" | 50 , 1000 |
"float" | 95.5 , 3.14 |
"bool" or "boolean" | true , false |
"list" | ["item1", "item2"] |
"list[str]" | ["item1", "item2"] |
"list[int]" | [1, 2, 3] |
"list[float]" | [1.5, 2.7, 3.14] |
"dict" | {"key": "value"} |