The following endpoint will be released in version 0.2.x (part of the mobile application API update). Please check the version here before attempting to use this endpoint.

Resource URL

Returns n affiliation identified by contact id.

GET /affiliations/:id

Handling the response

Below is a table of available response fields and objects that are returned within the response object of the returned object. The optional fields and objects can be requested in the _fields parameter; see included examples. Underlined values are default.

If you can't find the field you are after, you are probably thinking of a contact field. Please see the contact endpoints.

idunsigned int A unique id assigned to the contact
mobilestring 
emailstring 
faxstring 
positionstringe.g, Software Engineer or CEO
phonestring 
postal_addressunsigned intPostal address unique identifier
postal_address(<args>)objectPostal address object, including any requested optional fields.
physical_addressunsigned intPhysical address unique identifier.
physical_address(<args>)objectPhysical address object.
contactunsigned intContact object id. e.g, 124.
contact(<args>)objectContact object.
companyunsigned intCompany object id, e.g, 324
company(<args>)objectCompany object.
statusunsigned intThe contact's status id.
status(<args>)objectThe contact's status object with any optional fields.
default_affiliationunsigned intThe contact's default affiliation id.
date_modifiedunix ts 
date_last_interactedunix ts 
standingString 

Fields that can be object indicate the field can be requested as a resource. For example.

GET /affiliations/1.json?_fields=status

would return the status id. Where as,

GET /affiliations/1.json?_fields=status()

would return the status object, including any optional fields or objects within the parenthesis.