CRM APIs
Contact details for the provided identifier
HTTP method | GET |
URI | https://api.rambase.net/collaboration/contacts/{contactId} |
Supported formats | Xml, Html, Json (ex. $format=json) |
- URI parameter {contactId} |
Contact identifier
Integer, minimum 10000 |
Custom fields | Custom fields supported |
Successful HTTP status code | 200 |
API resource identifier | 160, version 39 |
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 are required/mandatory.
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.
$showDomainDescriptions Boolean, optional | Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false. |
$lang String, optional | Specifies the language used in the response, following the 3-letter ISO-639-1 [lll] |
$access_token String, optional | After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time. |
$db String, optional | Set the database/company for the request |
$format String, optional | Set the format of the response to use for the request. Accepted values are "xml", "html", "jsonstream", "json" |
$useMinimumVersion Integer, optional | Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information. |
$select String, optional | Use to define the fields to return in the response. Accepts a comma-separated list of field names. See the Expand and select page for more information. |
$expand String, optional | Use to include output fields that are not returned by default in the response. Accepts a comma-separated list of expandable field names. See the Expand and Select page for more information. |
$showCustomFields Boolean, optional | Set to "true" to include custom fields. Default value is false. |
Read more about filters and sorting on how to use filter parameters and named filters.
Read more 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.
ContactId
Contact identifier
>{Integer}</ContactId>CreatedAt
Date and time of creation
>{Datetime}</CreatedAt>UpdatedAt
Date and time of update
>{Datetime}</UpdatedAt>Status
Status of the contact. 1:New, 4:Active, 9:Inactive
Possible domain values can be found here
>{Integer}</Status>FirstName
Firstname/givenname of the contact
>{String}</FirstName>LastName
Surname/familyname/lastname of the contact
>{String}</LastName>JobTitle
Professional title
>{String}</JobTitle>ExternalPrivileges
Privileges to external applications for contact
Possible domain values can be found here
>{String}</ExternalPrivileges>PreferredLanguage
Three character code following the ISO 639-2 standard.
Possible domain values can be found here
>{String}</PreferredLanguage>Category
Category of the contact
Possible domain values can be found here
>{String}</Category>Source
Source of which the personal information was obtained
Possible domain values can be found here
>{Integer}</Source>HasAcceptedPrivacyPolicy
Privacy policy accepted. Yes or no value.
>{Boolean}</HasAcceptedPrivacyPolicy>HasMarketingConsent
Consent to marketing. Yes or no value.
>{Boolean}</HasMarketingConsent>LegalBasisForDataProcessing
The legal basis for processing contact's data
Possible domain values can be found here
>{Integer}</LegalBasisForDataProcessing>ContactId
Contact identifier
": "{Integer}",CreatedAt
Date and time of creation
": "{Datetime}",UpdatedAt
Date and time of update
": "{Datetime}",Status
Status of the contact. 1:New, 4:Active, 9:Inactive
Possible domain values can be found here
": "{Integer}",FirstName
Firstname/givenname of the contact
": "{String}",LastName
Surname/familyname/lastname of the contact
": "{String}",JobTitle
Professional title
": "{String}",ExternalPrivileges
Privileges to external applications for contact
Possible domain values can be found here
": "{String}",PreferredLanguage
Three character code following the ISO 639-2 standard.
Possible domain values can be found here
": "{String}",Category
Category of the contact
Possible domain values can be found here
": "{String}",Source
Source of which the personal information was obtained
Possible domain values can be found here
": "{Integer}",HasAcceptedPrivacyPolicy
Privacy policy accepted. Yes or no value.
": "{Boolean}",HasMarketingConsent
Consent to marketing. Yes or no value.
": "{Boolean}",LegalBasisForDataProcessing
The legal basis for processing contact's data
Possible domain values can be found here
": "{Integer}"
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 100052 HTTP 403 | You only have admittance to your own contacts |