REST API CONTACTS
POST /v1/crm/contacts
Creates or updates a contact.
If no ‘externalIntegrationId‘ is present, the contact’s first name, last name and email address (case insensitive) are used to match a contact to an existing contact in Priava.
A new contact will be created only if one cannot be matched.
When a user provides an organisation:
- If the organisation exists, it is associated to the existing organisation and no changes are made to the organisation properties.
- If the organisation does not exist, the organisation will be created with the contact’s telephone numbers and email address. The contact will also be associated to this newly created organisation.
Request:
A JSON POST request body expecting APIToken in the request header which re-authenticates the user with each request.
The contact’s first name.
The contact’s last name.
The contact’s primary email address.
The contact’s title. Must match list of Title’s in the tenant’s Priava system. e.g. Mr, Mrs etc.
The contact’s Job Title.
The contact’s department e.g. Accounts.
The contact’s debtor number.
The contact’s external integration ID. Hidden from the Priava UI, but can be used to store a foreign integration key.
The source of the integration e.g. name of your application.
The contact’s external reference number – used as a foreign key that is visibile on the Priava UI.
True / False – whether the contact should be opted out from marketing emails.
True / False – whether the contact has provided consent to store personal information.
phoneNumber stringThe contact’s phone number.
The contact’s mobile number.
The contact’s Organisation / Company name.
The organisation type – must match the CRM organisation types in the Priava tenant’s system. Will only be used if the organisation does not exist and is being created.
The organisation market sector – must match the CRM organisation market sectors in the Priava tenant’s system. Will only be used if the organisation does not exist and is being created.
The contact’s organisation/site address. See below for address properties required.
The contact’s postal address. See below for address properties required.
Any other address to be stored for the contact. See below for address properties required.
True / False – whether the contact is inactive or active in the system.
*Either a phone or mobile number is required (not both) in order to create a contact.
All addresses should be formatted as below.
Line 1 of the address.
Line 2 of the address.
Line 3 of the address.
The suburb for the address.
The state for the address.
The postcode / zip for the address.
The country for the address. A list of valid country entries can be found here.