PUT collaboration/contacts/{contactId}

Update information for specified contact

Note: Log in to check if your API client have access to run this resource
Version: 14
Success HTTP Status Code: 200

Uri parameters

{contactId} Integer Contact identifier

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold is required/mandatory.

Format:
1
<Contact
Contact

This field is optional.

>
2
     <FirstName
FirstName

Firstname/givenname of the contact

This field is optional.

>
{String}</FirstName>
3
     <LastName
LastName

Surname/familyname/lastname of the contact

This field is optional.

>
{String}</LastName>
4
     <JobTitle
JobTitle

Professional title

This field is optional.

>
{String}</JobTitle>
5
     <Category
Category

Category of the contact

Applicable domain values can be found here when logged in

This field is optional.

>
{String}</Category>
6
     <ExternalPrivileges
ExternalPrivileges

Privileges to external applications for contact

Applicable domain values can be found here when logged in

This field is optional.

>
{String}</ExternalPrivileges>
7
     <PreferredLanguage
PreferredLanguage

Three character code following the ISO 639-2 standard.

Applicable domain values can be found here when logged in

This field is optional.

>
{String}</PreferredLanguage>
8
     <Source
Source

Source of which the personal information was obtained

Applicable domain values can be found here when logged in

This field is optional.

>
{Integer}</Source>
9
     <Privacy
Privacy

This field is optional.

>
10
          <LegalBasisForDataProcessing
LegalBasisForDataProcessing

The legal basis for processing contact's data

Applicable domain values can be found here when logged in

This field is optional.

>
{Integer}</LegalBasisForDataProcessing>
11
          <HasAcceptedPrivacyPolicy
HasAcceptedPrivacyPolicy

Privacy policy accepted. Yes or no value.

This field is optional.

>
{Boolean}</HasAcceptedPrivacyPolicy>
12
          <HasMarketingConsent
HasMarketingConsent

Consent to marketing. Yes or no value.

This field is optional.

>
{Boolean}</HasMarketingConsent>
13
     </Privacy>
14
</Contact>
1
{
2
     "contact
Contact

This field is optional.

":
{
3
          "firstName
FirstName

Firstname/givenname of the contact

This field is optional.

":
"{String}",
4
          "lastName
LastName

Surname/familyname/lastname of the contact

This field is optional.

":
"{String}",
5
          "jobTitle
JobTitle

Professional title

This field is optional.

":
"{String}",
6
          "category
Category

Category of the contact

Applicable domain values can be found here when logged in

This field is optional.

":
"{String}",
7
          "externalPrivileges
ExternalPrivileges

Privileges to external applications for contact

Applicable domain values can be found here when logged in

This field is optional.

":
"{String}",
8
          "preferredLanguage
PreferredLanguage

Three character code following the ISO 639-2 standard.

Applicable domain values can be found here when logged in

This field is optional.

":
"{String}",
9
          "source
Source

Source of which the personal information was obtained

Applicable domain values can be found here when logged in

This field is optional.

":
"{Integer}",
10
          "privacy
Privacy

This field is optional.

":
{
11
               "legalBasisForDataProcessing
LegalBasisForDataProcessing

The legal basis for processing contact's data

Applicable domain values can be found here when logged in

This field is optional.

":
"{Integer}",
12
               "hasAcceptedPrivacyPolicy
HasAcceptedPrivacyPolicy

Privacy policy accepted. Yes or no value.

This field is optional.

":
"{Boolean}",
13
               "hasMarketingConsent
HasMarketingConsent

Consent to marketing. Yes or no value.

This field is optional.

":
"{Boolean}"
14
          }
15
     }
16
}

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$db String, optional Set the database to use for the request
$format String, optional Set the format of the response to use for the request. Accepted values are "xml", "json"
$lang String, optional Use to get localized responses. Supported formats are 3-letter ISO-639-1 [lll], 2-letter ISO-639-2 [ll], or a combination of a two-letter language code and a two-letter country code ISO-639-2 and ISO-3166-1 [ll_CC], [ll-CC]
$useMinimumVersion Integer, optional This can be used to test a new version of a resource when your ApiClient is running an older, deprecated, version of a resource. $useminimumversion can be used to test against a newer version of the resource. See the Deprecated APIs page for more information about this.

See the page about filters and sorting on how to use filter parameters and named filters.

See the page about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
1

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 100034 HTTP 404 Contact not found
Error 100044 HTTP 400 Current owner {0} still uses this contact for document handling
Error 100010 HTTP 400 {0} must be unique
Error 102529 HTTP 404 RamBase event type not found
Error 100009 HTTP 400 Missing required input arguments
Error 100012 HTTP 400 {0} must exist in {1}
Error 100045 HTTP 400 Can not delete reference {0} because it still uses this contact
Error 100264 HTTP 400 Both contact identifier and identifier that the contact should be linked to are required
Error 100031 HTTP 404 Customer not found
Error 100006 HTTP 400 Invalid document identifier: {0}
Error 100036 HTTP 400 Missing required input parameter: {0}
Error 100047 HTTP 404 Supplier not found
Error 100027 HTTP 400 Missing mandatory parameter {0}
Error 100051 HTTP 400 When logged in as supplier {0} you do not have access to this API resource
Error 100055 HTTP 403 You have only admittance to your own objects
Error 101119 HTTP 404 Shipping Service document not found
Error 101304 HTTP 404 Carrier not found
Error 102738 HTTP 404 Price list not found
Error 100050 HTTP 403 No admittance as customer {0}
Error 100053 HTTP 403 You have only admittance to your own suppliers
Error 101420 HTTP 404 Setting definition not found
Error 100048 HTTP 400 Parameter {0}: {1} not valid
Error 101514 HTTP 400 Setting definition reference is required
Error 101708 HTTP 400 Default value is required
Error 101640 HTTP 400 Data type is required
Error 101015 HTTP 404 Permission not found