Persons are your contacts, the customers you are doing Deals with. Each Person can belong to an Organization. Persons should not be confused with Users.
GET Get all persons/persons
GET Get details of a person/persons/:id
POST Add a person/persons
PUT Update a person/persons/:id
DELETE Delete a person/persons/:id
DELETE Delete multiple persons in bulk/persons
GET List files attached to a person/persons/:id/files
GET List e-mail messages associated with a person/persons/:id/emailMessages
GET List followers of a person/persons/:id/followers
GET List products associated with a person/persons/:id/products
GET List deals associated with a person/persons/:id/deals
GET List updates about a person/persons/:id/updates
GET List activities associated with a person/persons/:id/activities
GET List permitted users/persons/:id/permittedUsers
POST Merge two persons/persons/:id/merge
GET Find persons by name/persons/find
PersonFields represent the near-complete schema for a Person in the context of the company of the authorized user. Each company can have a different schema for their Persons, with various custom fields. In the context of using PersonFields as a schema for defining the data fields of a Person, it must be kept in mind that some types of custom fields can have additional data fields which are not separate PersonFields per se. Such is the case with monetary, daterange and timerange fields – each of these fields will have one additional data field in addition to the one presented in the context of PersonFields. For example, if there is a monetary field with the key 'ffk9s9' stored on the account, 'ffk9s9' would hold the numeric value of the field, and 'ffk9s9_currency' would hold the ISO currency code that goes along with the numeric value. To find out which data fields are available, fetch one Person and list its keys.
GET Get all person fields/personFields
GET Get one person field/personFields/:id
POST Add a new person field/personFields
DELETE Delete a person field/personFields/:id
DELETE Delete multiple person fields in bulk/personFields
Persons are your contacts, the customers you are doing Deals with. Each Person can belong to an Organization. Persons should not be confused with Users.
GET Get all persons/persons GET Get details of a person/persons/:id POST Add a person/persons PUT Update a person/persons/:id DELETE Delete a person/persons/:id DELETE Delete multiple persons in bulk/persons
GET List files attached to a person/persons/:id/files GET List e-mail messages associated with a person/persons/:id/emailMessages GET List followers of a person/persons/:id/followers GET List products associated with a person/persons/:id/products GET List deals associated with a person/persons/:id/deals GET List updates about a person/persons/:id/updates GET List activities associated with a person/persons/:id/activities GET List permitted users/persons/:id/permittedUsers POST Merge two persons/persons/:id/merge
GET Find persons by name/persons/find
PersonFields represent the near-complete schema for a Person in the context of the company of the authorized user. Each company can have a different schema for their Persons, with various custom fields. In the context of using PersonFields as a schema for defining the data fields of a Person, it must be kept in mind that some types of custom fields can have additional data fields which are not separate PersonFields per se. Such is the case with monetary, daterange and timerange fields – each of these fields will have one additional data field in addition to the one presented in the context of PersonFields. For example, if there is a monetary field with the key 'ffk9s9' stored on the account, 'ffk9s9' would hold the numeric value of the field, and 'ffk9s9_currency' would hold the ISO currency code that goes along with the numeric value. To find out which data fields are available, fetch one Person and list its keys.
GET Get all person fields/personFields GET Get one person field/personFields/:id POST Add a new person field/personFields DELETE Delete a person field/personFields/:id DELETE Delete multiple person fields in bulk/personFields