Location attributes model a physical location in the world. We store all location properties (address lines, postcode, country code, etc) on a single attribute value, rather than separate attributes. This means that when working with locations, updates must be atomic—every property must be specified, even if it is null. You’ll find an example of this attribute asDocumentation Index
Fetch the complete documentation index at: https://docs.attio.com/llms.txt
Use this file to discover all available pages before exploring further.
primary_location on both person and company objects.
Locations have the following properties:
line_1- the first line of the address, e.g."1 Infinite Loop"line_2- the second line of the address e.g."Block 1"line_3,line_4, same as abovelocality- the town, neighbourhood or area, e.g."Cupertino"region- the state, county, province or region, e.g."CA"postcode- the postal or zip code, e.g."95014"country_code- the ISO 3166-1 alpha-2 country code, e.g.USlatitude- latitudinal coordinates, e.g."37.331741"longitude- longitudinal coordinates, e.g."-122.030333"
Reading values
Depending on your use case, there are various properties of a location that might be relevant for you. The API will return the full object as structured data, without attempting to format it:Writing values
When writing location values, Attio will intelligently parse strings into structured location data.null.
Filtering
The propertiesline_1, line_2, line_3, line_4, locality, region and postcode can all be filtered by $eq, $contains, $starts_with and $ends_with operators.
The property country_code can be filtered by $eq and $starts_with operators.