Skip to main content

Define a field

Each key in fields is a field name. Its value is either a description or a typed object. The original routes take the same object as struct.
Field names must be letters, numbers and underscores. The description is what the agent researches, so say exactly what you want: "Current job title at the company in the input" beats "title". Use a typed object for every field that isn’t a string (details below).

Types

Parse dict values client-side with json.loads() (Python) or JSON.parse() (JavaScript).

Enums

Use enum when your code filters, groups or routes on the value. The value is always one of the options you list, so "Series A" never comes back as "series-a round". Use list[enum] when more than one option can apply. enum and list[enum] require a non-empty options list.

Nested objects

object and object_list take subfields: a list of {"key", "type", "description"} objects. A subfield can be any type, including object and object_list with subfields of their own, at any depth; enum and list[enum] subfields take options. type defaults to string and description is optional.
A nested object_list returns as a list of objects inside each entry:

Missing values

Every field you request is present in the response. A field the agent couldn’t establish is null (Company Intelligence returns [] for list fields). Values are never invented to satisfy a type.

How each endpoint resolves types

Only typed objects return the same type on every People and Company Intelligence request. A bare type name ("int") returns that type with no description, and an example value (50) returns a string, except on Company Intelligence with full_org_chart: true, which reads a bare type name as a description and returns an example value as its own type.

Type casting

When a researched value doesn’t match its field’s type, Sixtyfour converts it only if the conversion loses nothing: Nothing else is cast: "about 50" never becomes 50.

Input fields in the output

On the original People Intelligence routes, fields you send in lead_info but don’t list in struct come back in structured_data unchanged, with their original values and types. Fields you do list in struct are researched and returned with the struct’s type, even if you sent a value for them.
There is no image type. A field whose description asks for an image (a headshot, a logo, a screenshot) is an ordinary string field whose value is a permanent image URL hosted by Sixtyfour. See Image fields.