API

Collaboration APIs

GET collaboration/emails/{emailId}

Email details for provided identifier

HTTP method GET
URI https://api.rambase.net/collaboration/emails/{emailId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {emailId} Email identifier
Integer, minimum 100000
Successful HTTP status code 200
API resource identifier 1899, version 10

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.

Format:
1
1

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.

$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.

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.

Format:
1
<Email>
2
     <EmailId
EmailId

Email identifier

>{Integer}</EmailId>
3
     <Status
Status

Status of the relationship email

>{Integer}</Status>
4
     <CreatedAt
CreatedAt

Date and time of creation

>{Datetime}</CreatedAt>
5
     <OccuredAt
OccuredAt

Date and time of the relationship activity

>{Datetime}</OccuredAt>
6
     <Subject
Subject

Subject of the relationship email

>{String}</Subject>
7
     <Body
Body

Body/message of the relationship email

>{String}</Body>
8
     <Direction
Direction

Indicates whether the relationship activity is inbound (INBOUND) or outbound (OUTBOUND).

>{String}</Direction>
9
     <Regarding
Regarding

The customer/supplier of the relationship

>
10
          <ObjectId
ObjectId

Identifier of the object

>{Integer}</ObjectId>
11
          <ObjectType
ObjectType

Type of object

>{String}</ObjectType>
12
          <Name
Name

Name of the customer/supplier, or last name if it is a person.

This field is greyed out because it is an expandable field. You have to add $expand=Regarding.Name in your request URI to get this field

>{String}</Name>
13
          <FirstName
FirstName

First name of the customer/supplier

This field is greyed out because it is an expandable field. You have to add $expand=Regarding.FirstName in your request URI to get this field

>{String}</FirstName>
14
          <ObjectLink
ObjectLink

API reference to the object

>{String}</ObjectLink>
15
     </Regarding>
16
     <CreatedBy
CreatedBy

All activities are assigned an owner who is responsible for completing/follow up the activity

>
17
          <UserId
UserId

User identifier

>{Integer}</UserId>
18
          <Name
Name

Name of the user

This field is greyed out because it is an expandable field. You have to add $expand=CreatedBy.Name in your request URI to get this field

>{String}</Name>
19
          <FirstName
FirstName

First name of the user

This field is greyed out because it is an expandable field. You have to add $expand=CreatedBy.FirstName in your request URI to get this field

>{String}</FirstName>
20
          <UserLink
UserLink

User reference

>{String}</UserLink>
21
     </CreatedBy>
22
     <Sender
Sender

Reference to the contact/supplier/employee/customer who sent the email

>
23
          <EmailAddress
EmailAddress

Email address of the sender

>{String}</EmailAddress>
24
          <Description
Description

Description of sender

>{String}</Description>
25
          <ObjectReference
ObjectReference

Reference to the contact/supplier/employee/customer who sent the email

>
26
               <ObjectId
ObjectId

Identifier of the object

>{Integer}</ObjectId>
27
               <ObjectType
ObjectType

Type of object

>{String}</ObjectType>
28
               <ObjectLink
ObjectLink

API reference to the object

>{String}</ObjectLink>
29
          </ObjectReference>
30
     </Sender>
31
</Email>
1
{
2
     "email": {
3
          "emailId
EmailId

Email identifier

": "{Integer}",
4
          "status
Status

Status of the relationship email

": "{Integer}",
5
          "createdAt
CreatedAt

Date and time of creation

": "{Datetime}",
6
          "occuredAt
OccuredAt

Date and time of the relationship activity

": "{Datetime}",
7
          "subject
Subject

Subject of the relationship email

": "{String}",
8
          "body
Body

Body/message of the relationship email

": "{String}",
9
          "direction
Direction

Indicates whether the relationship activity is inbound (INBOUND) or outbound (OUTBOUND).

": "{String}",
10
          "regarding
Regarding

The customer/supplier of the relationship

": {
11
               "objectId
ObjectId

Identifier of the object

": "{Integer}",
12
               "objectType
ObjectType

Type of object

": "{String}",
13
               "name
Name

Name of the customer/supplier, or last name if it is a person.

This field is greyed out because it is an expandable field. You have to add $expand=Regarding.Name in your request URI to get this field

": "{String}",
14
               "firstName
FirstName

First name of the customer/supplier

This field is greyed out because it is an expandable field. You have to add $expand=Regarding.FirstName in your request URI to get this field

": "{String}",
15
               "objectLink
ObjectLink

API reference to the object

": "{String}"
16
          },
17
          "createdBy
CreatedBy

All activities are assigned an owner who is responsible for completing/follow up the activity

": {
18
               "userId
UserId

User identifier

": "{Integer}",
19
               "name
Name

Name of the user

This field is greyed out because it is an expandable field. You have to add $expand=CreatedBy.Name in your request URI to get this field

": "{String}",
20
               "firstName
FirstName

First name of the user

This field is greyed out because it is an expandable field. You have to add $expand=CreatedBy.FirstName in your request URI to get this field

": "{String}",
21
               "userLink
UserLink

User reference

": "{String}"
22
          },
23
          "sender
Sender

Reference to the contact/supplier/employee/customer who sent the email

": {
24
               "emailAddress
EmailAddress

Email address of the sender

": "{String}",
25
               "description
Description

Description of sender

": "{String}",
26
               "objectReference
ObjectReference

Reference to the contact/supplier/employee/customer who sent the email

": {
27
                    "objectId
ObjectId

Identifier of the object

": "{Integer}",
28
                    "objectType
ObjectType

Type of object

": "{String}",
29
                    "objectLink
ObjectLink

API reference to the object

": "{String}"
30
               }
31
          }
32
     }
33
}

Possible error codes the response might return:

Error 100050 HTTP 403 No admittance as customer {0}
Error 100053 HTTP 403 You have only admittance to your own suppliers